Shareware Overload Trio 2

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Overload Trio 2 / Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO / dir42 / fxlst4.zip / FXLST4.TXT

Wrap

Text File | 1994-04-04 | 1MB | 19,892 lines

CLARION Database Developer Anomalies and Fixes Ascii Report as of 4/04/94 COPYRIGHT 1985, 1986, 1988, 1990, 1992, 1993 by Clarion Software Corporation All Rights reserved. ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0015 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 4/09/93 │ │ Reported In : 3002 RevisedDate : 1/25/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Mouse support needs to be added to the pulldown menu │ │ generator!! │ │ Q & A: 3.1 Issue │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0209 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/93 │ │ Reported In : 3001 RevisedDate : 1/25/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ One of the things that has always bugged me about Clarion │ │ is the way it removes the leading 0 from a date. It makes │ │ reports look funny. I was hoping that version 3 would fix │ │ this, but not so. │ │ Can you add to the wish list, a new Date Option so that if │ │ we want the leading 0, we can have it? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0269 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/05/93 │ │ Reported In : 3001 RevisedDate : 1/25/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 8. Can't use hotkeys to activate "Change/Ok/Cancel" on the │ │ "Select Color for Entry Field" screens. Also, same problem │ │ on the lower buttons of the Track Draw selection screen. │ │ (Tested OK PAS) │ │ Suggestion: │ │ 9. P L E A S E !!!! make RADIO BUTTONS available on the │ │ PULLDOWN menu item type selection. Or else allow entry of │ │ source associated with menu items (toggles etc). Case in │ │ point, a pulldown choice of LPT ports to "check" the │ │ desired destination. It looses something in the translation │ │ if you have to go to a FORM/SCREEN procedure type │ │ (primarily due to the pulldown disappearing). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0358 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 4/09/93 │ │ Reported In : 3002 RevisedDate : 1/26/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ no multi record selecting unless it is to be done │ │ differently than 2.1. If it is then change the status of │ │ this to NEED/INFO │ │ Using a two componet key, Right now it just selects on the │ │ second componet only regardless of the first. Because of │ │ this I ask the question are we looking at all records when │ │ record selecting....we must be since I got all of my │ │ records where the second componet was correct. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0405 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/18/93 │ │ Reported In : 3001 RevisedDate : 1/26/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ FORM TEMPLATE PROCEDURE │ │ I have encountered the following: │ │ 1: The "REQ" attribute doesn't work on entry fields. │ │ 2: App Gen doesn't generate the range checking code on │ │ entry fields when a range is defined in the dictionary, │ │ ie: Field "X" should only accept values between 5 and │ │ 50, but AppGen doesn't insert the necessary code. │ │ 3: App Gen doesn't handle an auto-increment on a │ │ multi-component key correctly. │ │ 4: In the BROWSE procedure type, the Range Limit and │ │ Range Value fields don't seem to be working correctly. │ │ 5: I've had several keyboard lockups inside the │ │ environment. │ │ I doubt if any of the above is new to you, but I just │ │ wanted to get my 2 cents in. I may not be doing somethoing │ │ correctly on item 4. Are ther any sample .APPs out there to │ │ show the proper way to show a Browse certain key value, │ │ like a simple invoice program? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0408 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/18/93 │ │ Reported In : 3001 RevisedDate : 1/26/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Pulldown Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In case it hasn't been suggested or requested, a MSG │ │ attribute for PullDown items would be a very nice addition. │ │ R&D: Implemented in 3005 in Library, but no access to MSG │ │ attribute in the Pulldown Menu Formatter yet. Requires an │ │ App format change. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0470 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/93 │ │ Reported In : 3002 RevisedDate : 1/26/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Operating System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using Lantastic: │ │ I found out if I loaded SERVER.exe locally __AND__ logged │ │ into my machine (I don't even have to "NET USE" any local │ │ resources), the "bleep" went away. If I then logged out, │ │ the "bleep" came back. │ │ REDIR.exe MYCPU │ │ SERVER.exe │ │ NET LOGIN \\MYCPU <---- At this point the bleep is │ │ gone, as long as I am logged │ │ into "MYCPU" │ │ NET LOGOUT \\MYCPU <---- At this point the bleep is │ │ back. │ │ Further I can even remove SERVER.exe via the command line │ │ or Ctrl_Alt_DEL, and the bleep stays away as long as I │ │ don't logout of my local machine before I remove Server, │ │ ie: │ │ REDIR.exe MYCPU │ │ SERVER.exe │ │ NET LOGIN \\MYCPU <---- At this point the bleep is │ │ gone, as long as I am logged │ │ into "MYCPU" │ │ SERVER.exe /REMOVE <---- At this point the bleep is │ │ still gone, even though Server │ │ is no longer loaded. REDIR │ │ apparently still thinks I'm logged into │ │ myself. If I subsequently"NET LOGOUT //MYCPU" │ │ the bleep is comes back │ │ again. │ │ Also, for what its worth, SHARE doesn't matter in the above │ │ mix, I've tried it both with and without SHARE loaded. │ │ Obviously, LANtastic is partially at fault, CDD .exe's work │ │ fine under straight DOS, therefore, LANtastic is not │ │ behaving as 100% DOS compatible. │ │ However, I would personally hesitate to put all the blame │ │ on LANtastic, since this is the first time this has ever │ │ happened on my system, I think CDD3 must be doing something │ │ fairly unusual. I test most major commercial packages, │ │ including other beta products, and this has never happened │ │ before. │ │ R & D: Sent to England │ │ R&D: What is he talking about? What beep? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0529 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/08/93 │ │ Reported In : 3002 RevisedDate : 1/26/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3) The multi-valued global symbol %RelationalAccessFlds is │ │ returning an improper value in some cases. The code below │ │ was generated in a number of cases where all three files │ │ are defined with the same fields and keys. Only one of the │ │ files generated the spurious link field; the other three │ │ fields (uncommented ones) are correct; the last one │ │ generates a compiler error. │ │ BBTopics:Linkto:BBC:SysID LIKE(BBC:SysID) │ │ BBSubjct:Linkto:BBT:SysID LIKE(BBT:SysID) │ │ BBMessgs:Linkto:BBS:SysID LIKE(BBS:SysID) │ │ !BBMessgs:Linkto:BBM:DescKey LIKE(BBM:DescKey) │ │ 4) Maybe related to #3; when attempting to add a record │ │ thru the procedure (form) where that error occurred, I get │ │ an error screen generated from the RelationalUpdate │ │ routine, as follows: │ │ The transaction cannot be completed │ │ at this time. The error posted was: │ │ unable to log transaction │ │ The Clarion errorcode is 48; the DOS error 2 is spurious, │ │ since the records for the file have been displayed in a │ │ table already; FILE NOT FOUND _must_ be wrong! │ │ Q&A: │ │ 3) send example │ │ 4) sounds like the file schema for the form is naming the │ │ wrong Primary file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4072 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tim Murray 73174,3645 MSG#:58936 │ │ New with the 5th template release. │ │ If you try to delete a record that won't delete because of │ │ a relation with another file (Prohibit delete), the program │ │ tells you, you hit OK, the record remains locked. │ │ If you go and delete the child records and try to come │ │ back and delete this parent record, it says that it is │ │ locked by another user. │ │ R&D: Fixed in 3007.2 release. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 0723 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 4/01/93 │ │ Reported In : 3002 RevisedDate : 1/26/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have defined a Clarion file in my dictionary with fields, │ │ keys, memos, etc. I then decide that I want this to be an │ │ ASCII file. The keys, memos, and relations are dimmed out, │ │ and a message appears at the bottom of the listboxes that │ │ say "Not Supported"... HOWEVER, if I use the "Generate │ │ Source" option, the keys and memos are generated in that │ │ source! The same goes for generating source in the app │ │ generator. │ │ R & D : This will be addressed in a future release. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4071 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you try to view an ascii file on the network in HEX mode │ │ and you do NOT have read/write access to the file you will │ │ xtrace. │ │ I know that this is a very dumb thing to do but I figure │ │ any xtrace should be reported. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 1874 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 1/26/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Bayliss 100025,1577 │ │ When in _continuous_ select mode (IE when doing form │ │ validation) a PRESS cannot be used to enter data into an │ │ entry form │ │ Therefore if you have a field with a lookup as a │ │ SELECT routine it will not work if invalid data gets into │ │ that field. (The lookup template returns results using │ │ PRESS) │ │ DAB │ │ Q&A: This is due to the use of PRESS in the templates. │ │ Until they are changed this is going to happen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 1412 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 6/01/93 │ │ Reported In : 3003 RevisedDate : 2/01/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Setup procs for entries still do not work. │ │ In the template under of no records; when there are no │ │ records with an update proc; code fro record not added │ │ appears twice. │ │ Mulitcomponet range limits: │ │ When adding a record that does not meet the range limit; │ │ the list box only gets the first record upon returning. │ │ We need to restore range limit when the insert button is │ │ used; like when you are in the listbox and press insert │ │ Maybe if we restore range limits when coming out of │ │ updateproc and save range limits as setup to list then │ │ we could use entry fields to fill the range limits │ │ Q & A : In a similar situation Placing code in a Locator │ │ field in the 'When Selected Area' will not get │ │ executed even when Enable Hot Records is selected. │ │ The above reports are not fixed in 3005. │ │ R&D: Fixed in Template Release 3007.101 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 1862 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David L. Shapiro 72122,330 │ │ I found a few more problems with building reports: │ │ 1) I can not build a report using a concatenated key. │ │ The problem is exactly the same as the browse procedure │ │ had in v3002 where the file SET and the out of range │ │ check is only done on the Range Limit Field and not on │ │ all the preceeding key values. │ │ 2) If I only enter a Range Limit Field and compile, │ │ I get a pre-compiler error "You must enter a Range │ │ Value Field." When I enter a Range Value Field, I │ │ still get the error I just mentioned, although it │ │ does compile. │ │ TB: I changed this from a suggestion to a problem since │ │ this was not a problem in 2.1 without writing any code │ │ other than field=field. │ │ R&D: I believe that these problems are fixed in 3007.2. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 1969 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 7/22/93 │ │ Reported In : 3004 RevisedDate : 1/25/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Cliff Court 76645,177 │ │ 1 It seems that if you don't have the CREATE attribute on │ │ and you try to BUILD a btrieve file, you get Error 76, │ │ invalid index string. │ │ R&D: WOKOMM │ │ 2 It then seems that you have to not only OPEN the file, │ │ but read a record from it before attempting to BUILD. │ │ Otherwise you get ERROR 33, record not available. │ │ R&D: WOKOMM │ │ 3 One of our clients reported the following. He has an app │ │ that reads a bunch of ASCII records downloaded from a │ │ MainFrame. The app performs a number of different │ │ validations on each record. Each validation involves a │ │ number (1-10) of reads from various btrieve files (GETs & │ │ NEXTs). Finally therecord is APPENDed to a new btrieve │ │ file. The program takes 10 minutes to create the new │ │ btrieve file. If he places the APPEND statement inside │ │ comment then the program takes 30 secs. In other words │ │ the performance of the btrieve driver's APPEND seems to │ │ be somewhat lacking? The strange thing is that all the │ │ other file accesses appear to be comparitively fast. Is │ │ there something lacking in the default btrieve │ │ parameters? │ │ R&D: Must be doing the ADD on a local drive so does not get │ │ the benifit of the NLM speed. He can also use the │ │ different open modes to open the file in accelerated │ │ mode. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2124 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 8/13/93 │ │ Reported In : 3004 RevisedDate : 2/03/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user: when doing a make and debug and │ │ enable debug settings has not been marked, automatically │ │ have it do a make as if it was marked │ │ R&D: You would drive yourself crazy having to recompile │ │ the entire program each time. This is not a good idea. │ │ Maybe we could pop up a warning before continuing so you │ │ could fix the settings before attempting the run │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2188 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 8/23/93 │ │ Reported In : 3004 RevisedDate : 2/01/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ on a browse screen with a locator field, you cannot │ │ reference that field in source code. all other fields have │ │ a value except for the locator field │ │ R&D: Fixed in Template Release 3007.101 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2203 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : RB DateReported : 8/24/93 │ │ Reported In : RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about some sort of menu driven utility to view a │ │ Btrieve file's statistics <ala BTFILER/BTVIEWER> to help │ │ with file/key definition in the dictionary? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2458 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 9/26/93 │ │ Reported In : 3004 RevisedDate : 2/01/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ cannot use "when field is selected" for a locator field. │ │ if this is intended it should be documented in template │ │ help. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2645 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 10/14/93 │ │ Reported In : 3004 RevisedDate : 3/28/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ uploaded file from Jim Morgan regarding link errors and │ │ runtime errors. │ │ See file 2645.zip │ │ R & D : Cannot reproduce, No data file found. File not │ │ found is normal behavior. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2703 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 10/20/93 │ │ Reported In : 3004 RevisedDate : 2/01/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ : Douglas Johnson 75310,2035 MSG#:36818 │ │ This has been reported several times before, but it seems │ │ to not be of very high priority even though anyone using │ │ Browse (Lib or Dll) is potentially affected. │ │ When on the ?List field in a Browse procedure, if one │ │ selects another field but does not complete it (Tab/ShftTab │ │ out of ?List), the field setup code (CASE SELECTED) is not │ │ executed. This is because execution is never returned back │ │ from Browse.Lib. The culprit code in Browse.Cla is: │ │ ACCEPT │ │ .. OF ?List │ │ ... │ │ IF SELECTED() <> ?List THEN CYCLE. << Goes right │ │ back to AcceptInput │ │ PS - note from Debby │ │ The selected code for the first entry field on the browse │ │ does not get executed coming into the browse. If you are │ │ the list box and select any other field on the screen, the │ │ selected code does not execute. Regardless of hot records. │ │ Please do not mark this "user may have to enable hot │ │ records like you did the last XX#@#@ times this was │ │ reported. Even in response to David Bayliss. This is a │ │ problem even if hot records or enabled. Fine to say we │ │ won't fix it yet but don't mark it fixed in 3005 cause it │ │ ain't. <g> thanks │ │ R&D: Fixed in 3007.101 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2798 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 10/27/93 │ │ Reported In : 3006 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user 216856 -- using gui table deletekey to a │ │ form thenpresses ok and it loops forever -- 3006 -=- this │ │ only happens when using gui and when the last push │ │ button in field order is not ok or cancel, but instead │ │ some other push button. │ │ I don't make these up, I just report them. │ │ QA: I tried to duplicate this with the ORDERGUI app. I │ │ added a button to one of the forms. WOKOMM. Have the user │ │ send in his APP & DCT. I have a feeling he removed the CUA │ │ Attribute off the Screen and that is causing the problem. │ │ Ok. You win he has the Cua attribute off. That makes this │ │ a template bug then I think. Even if it is not in gui this │ │ happens. So it has nada to do with gui. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2863 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 11/02/93 │ │ Reported In : 3006 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Child Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In non-cua during add or change of a record, pressing the │ │ Save button causes a continuous loop │ │ R&D: I believe this has been fixed. I cannot reporduce │ │ the bug on my system, while during my initial tests (with │ │ old templates) I could. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2868 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/02/93 │ │ Reported In : 3006 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Bob Divine 76130,3536 MSG#:39895 │ │ There is a MAJOR problem with the browse template in 3006!! │ │ Want to try this one out?? Just make the ORDERS.APP in the │ │ example subdirectory with 3006. │ │ From the pulldown select Update Files. Select Products │ │ (procedure name is: BrowseProducts). │ │ Now, with the highlight bar on the first entry, double │ │ click the mouse anywhere on an empty space on the form ie: │ │ the open space under the listbox. Presto, the first field │ │ in the listbox goes blank! │ │ Now select the second item in the list. Double click again │ │ in some empty space and, not only does the first field in │ │ the second row go blank, the rest of the data elements take │ │ on the value of the data elements from line one. │ │ You can keep on going down the list, until the whole list │ │ has a blank first field and all other fields filled with │ │ the data from record one. │ │ QA: See test file!! If you remove the locator it does not │ │ happen!!!! Must be in Browse.cla somewhere! │ │ R&D: Repaired in 3007.100 Patch │ │ Updated in 3007.101 Template release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2892 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 11/03/93 │ │ Reported In : 3006 RevisedDate : 1/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Paradox Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when changing the same record on two workstations at the │ │ same time, instead of getting changed by another station, │ │ The error message of errorcode 33 record not available is │ │ returned. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2927 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/04/93 │ │ Reported In : 3006 RevisedDate : 2/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Operating System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mike Hanson, BoxSoft 73234,1447 MSG#:40225 │ │ I've got a problem running CSHELL under OS/2. If I select │ │ a floppy that is not available, I get a general protection │ │ and usually an XTRACE. It seems like your critical error │ │ handling code is not cutting it under OS/2. │ │ R&D: 1/10/94: Found that extender Critical Error handler │ │ expects real mode addresses from the underlying OS. OS/2 │ │ returns protected mode addresses. It seems like OS/2 is │ │ calling a DOS program with a protected mode address. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2939 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/05/93 │ │ Reported In : 3006 RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ With NLM 5.x you non-case sensitive sorting is controlled │ │ via the alternate collating sequence. The Clarion system │ │ allows you to use the CLACOLSEQ variable to specify an │ │ alternate collating sequence. However, this does not give │ │ true case insensitive sorting like Btrieve. Instead you │ │ have a<A<b<B... │ │ How about a method of specifying that a Btrieve ACS file is │ │ used when creating the file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2950 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/05/93 │ │ Reported In : 3006 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Operating System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: TIM FARRAR 75230,1165 MSG#:40579 │ │ Using LANTASTIC: I created a quick Clarion program that │ │ shows the status of each LPTx port and found that when LPT1 │ │ is CAPTUREd to a network printer, all three ports show a │ │ status of "1", which will not produce the error you mention. │ │ However, if LPT1 is not CAPTUREd, then only LPT1 has a │ │ status of "1", while the others show status of "0". For │ │ now,the workaround, of course, is to CAPTURE on LPT1 (a │ │ pain, but it works). Problem with capturing LPT2 or LPT3 │ │ status returns printer off line. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2968 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/08/93 │ │ Reported In : 3006 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ REALCALL is not exported in DESCLA.EXP. │ │ R&D:REALCALL is not exported from DESCLA, but rather from │ │ tsxlib. Indeed however, REALCALL is not exported. Sent to │ │ Nigel. │ │ SF2BC:REALCALL is in OS2LIB.A so can be exported │ │ R&D: Ok REALCALL is now exported from DESCLA.EXP │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 2991 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Wayne Freeman 76314,2100 MSG#:41496 │ │ I've taken care of a shortcoming in the InitFields routine │ │ in Clarion5.tpx, and I thought I'd share it with you. │ │ The shortcoming is that if you want to set an initial │ │ value on a dimensioned field, the generated code is missing │ │ all appropriate subscripts, causing syntax errors. │ │ Here's the original template code: │ │ #GROUP(%InitFields) │ │ #IF(%InitRoutine = 'TRUE') │ │ InitializeFields ROUTINE │ │ #FOR(%Field) │ │ #IF(%FieldInitial <> %NULL) │ │ %Field = %FieldInitial │ │ #ENDIF │ │ #ENDFOR │ │ #ENDIF │ │ Here are my proposed changes (worked for me): │ │ InitializeFields ROUTINE │ │ #FOR(%Field) │ │ #IF(%FieldInitial <> %NULL) │ │ #IF(%FieldDimension1) │ │ Loop Idx1# = 1 to %FieldDimension1 │ │ #IF(%FieldDimension2) │ │ Loop Idx2# = 1 to %FieldDimension2 │ │ #IF(%FieldDimension3) │ │ Loop Idx3# = 1 to %FieldDimension3 │ │ #IF(%FieldDimension4) │ │ Loop Idx4# = 1 to %FieldDimension4 │ │ %Field[Idx1#,Idx2#,Idx3#,Idx4#] = │ │ %FieldInitial End !Loop Dimension 4 │ │ #ELSE │ │ %Field[Idx1#,Idx2#,Idx3#] = │ │ %FieldInitial #ENDIF │ │ End !Loop Dimension 3 │ │ #ELSE │ │ %Field[Idx1#,Idx2#] = │ │ %FieldInitial #ENDIF │ │ End !Loop Dimension 2 │ │ #ELSE │ │ %Field[Idx1#] = │ │ %FieldInitial #ENDIF │ │ End !Loop │ │ Dimension 1 #ELSE │ │ %Field = │ │ %FieldInitial #ENDIF │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3026 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 11/11/93 │ │ Reported In : 3006 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ File from Jim Morgan showing bug in Linker Redirections │ │ cis id 72371,2444 │ │ tech proj 2654 │ │ R&D:This is a well documented problem with redirection in │ │ the make system. sent to RC │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3031 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 11/11/93 │ │ Reported In : 3006 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ file showing problem with deformat │ │ cs 71033,135 doug johnston │ │ ts 2658 │ │ file 3031.zip │ │ R&D:Very well documented problem outlining differences │ │ between 2.1 and 3.0. My opinion is that 3.0 is more │ │ logical but will defer the call to Bruce. │ │ **BB: Clarion standard: time midnight is 1. Both 24:00 and │ │ 0:00 should convert to 1. 1/100 past midnight is 2. It │ │ should work the same in 2.1 and 3.0. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3036 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 11/11/93 │ │ Reported In : 3006 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In RUNTIME.DOC, CLASYMBOLS has 13 values assigned to it as │ │ the example. As of Late Breaking News, LOADSYMBOLS uses 16 │ │ values due to smooth mouse (LBN, pg 8). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3044 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/12/93 │ │ Reported In : 3004 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joe Impac 71477,3013 MSG#:42257 │ │ If you use the date picture @d3 and the date involved is │ │ blank (0), the date is formatted as ' , ' instead │ │ of ' , '. │ │ -cindy cohen impac medical systems │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3092 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 11/17/93 │ │ Reported In : 3006 RevisedDate : 2/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David S. Moore 70761,470 MSG#:43025 │ │ I have just loaded up and compiled with 3006. I find that │ │ a non-CUA browse window still doesn't work correctly. When │ │ you press enter on the highlighted item, the program │ │ doesn't call the update procedure-- control just shifts to │ │ the locater field (if there is one.) Also, double-clicking │ │ with the mouse doesn't always select the correct record. I │ │ know that technical support acknowledged that this was a │ │ bona-fide bug in 3003. Any plans to fix it in a future │ │ release?? │ │ This is a new report. The database says fixed in 3001. It's │ │ still broke. tested Debby │ │ QA Note: │ │ This is really a matter of whether or NOT a LISTBOX should │ │ be completed by the ENTER KEY (ie should Accecpt be │ │ completed when EnterKey is pressed and the current field is │ │ a LISTBOX on a NON-CUA Screen). │ │ R&D: After trying a small test program, the ENTER key │ │ definately does complete the ACCEPT when coming from a list │ │ box, so something else is going on with the program other │ │ than low-level screen library I/O. │ │ R&D: This code SHOULD be fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3151 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 11/24/93 │ │ Reported In : 3006 RevisedDate : 1/25/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ uploaded file with key problems btreive │ │ file 3151.zip │ │ jon Fletcher 71413,3062 │ │ ts 2726 │ │ R&D: The zip file contains an app that relies on │ │ unsuppliedtemplates and there is no readme explaining how to │ │ reproduce the problem │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3176 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 11/30/93 │ │ Reported In : 3006 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when using EXTERNAL for a file, you will get a warning │ │ TYPE$CUS:RECORD is duplicated (dll) │ │ see enclosed example( extlib is the exe, lib is the dll) │ │ tech support project 2739 │ │ BC:It is generating the type$x:record in the module │ │ w/external used... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3187 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 12/02/93 │ │ Reported In : 3006 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Example file using the graphics library that crashes in │ │ protected mode but runs in real mode. │ │ see file 3187.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3191 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 12/02/93 │ │ Reported In : 3006 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in 3191.zip use of the INT86x API call causes invalid │ │ screen structure when exiting program │ │ R&D:Could not reproduce, however I was using newer version │ │ of API with serious bug fix in INT86X. INT86x used to be │ │ prototyped to take *GROUP as params. These should be │ │ *STRING... It is very likely this was the source of the │ │ problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3197 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 12/02/93 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Tested/OK │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CLA$ISDRIVE is only prototyped in getdir.inc. This should │ │ be placed in both.inc and cla_lib.inc. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3207 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 12/03/93 │ │ Reported In : 3006 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ _bioscom is not exported from DESCLA.EXP │ │ R&D: _bioscom is now exported │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3211 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 12/03/93 │ │ Reported In : 3006 RevisedDate : 1/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Paradox Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ .LCK file maintenance │ │ when a file is opened a filespec.LCK file is created and │ │ the paradox.net file is updated. if the shared file is │ │ closed while another user has it opened the lck file is │ │ removed. this causes problems with the user who still has │ │ the file open. they will get errors because an entry is │ │ found in the paradox.net file but no corresponding .lck │ │ file is found. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3225 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 12/07/93 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I found the help for the stop window for the first time, │ │ but now the info on that screen has changed, and it needs │ │ to be updated │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3229 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 12/07/93 │ │ Reported In : 3007b RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Example Applications │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This is a problem with the demo example ...or maybe with a │ │ template. When you go to the option with the child │ │ template.If you choose insert, instead of the appropriate │ │ ...change, the cancel off of the child. The record that │ │ was highlited actually is left with just a comma │ │ there. │ │ R&D: Repaired. Problem was that browse that called the │ │ child had insert and delete buttons, but no provision for │ │ entering that information. Removed Insert and Delete │ │ buttons, and changed the text of the ?CHANGE button to │ │ 'View Children' │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3234 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 12/07/93 │ │ Reported In : 3006 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Report Formatter Editor and Generator. user would like to │ │ beable to see the band lables in the formatter without going │ │ into the band properties screen. │ │ I changed this status to a problem as it is a problem. For │ │ one it is removing funtionality from 2.1 to 3.0. Anyone │ │ designing an extensive report will fight with this │ │ problem. Debby │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3259 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 12/09/93 │ │ Reported In : 3006 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you enter %O%%M%%C%mylib.lib in as an external library │ │ the project system converts it to %o%%m%%c%mylib.lib │ │ R&D:Bruce requested that the project system be case │ │ insensitive for the sake of users having to enter %clapfx%. │ │ I can't think of satisfactory work around, can you? │ │ SF2BC: Add %o,%m and %c to TSPRJ.TXT setting them equal to │ │ %O,%M and %C respectively. │ │ R&D:Ok, maybe this will work if it doesn't break 17 other │ │ things... It does feel a bit fudgy! │ │ R&D:Ok, anything it breaks is getting sent up to you SRF:) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3260 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 12/09/93 │ │ Reported In : 3006 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The following program only compiles in xlarge: │ │ PROGRAM │ │ MAP │ │ MODULE('InitMod') │ │ InitModules(LONG, LONG, <LONG>, <LONG>, <LONG>, <LONG>), │ │ |C, RAW, NAME('_InitModules'); END │ │ END │ │ _SYSTEM LONG, EXTERNAL, NAME('SYSTEM$') │ │ CODE │ │ InitModules(_SYSTEM,0) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3279 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 12/10/93 │ │ Reported In : 3006 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralph Johnston 71033,135 MSG#:46108 │ │ The FindClose function defined in the API is │ │ mis-documented. Even though it appears to be in the │ │ Clarion Standard Library, its real "NAME()" does NOT start │ │ with a CLA$. In other words, it is documented as: │ │ FindClose(*GROUP),RAW,NAME('Cla$findclose') but should be: │ │ FindClose(*GROUP),RAW,NAME('findclose') │ │ Notice the rather unusual lack of either the CLA$ prefix │ │ *or* the underscore prefix. │ │ ..Ralph │ │ documentatio bug │ │ R&D:Documentation and Code bug... fixed, including some │ │ other notes on problems in the API. *? should never be │ │ used to call standard C functions (this is _NOT_ void*) and │ │ neither is *GROUP useful (this is _NOT_ struct blarg *, it │ │ is unsigned len, char *, struct type *) *STRING,RAW │ │ should be used for almost all cases of "char *,struct │ │ blarg*,and void*". You must also use the RAW attibute to │ │ avoid sending the length of the string. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3309 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 12/14/93 │ │ Reported In : 3006 RevisedDate : 2/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: R.Radcliffe 72460,3560 MSG#:46679 │ │ In 3006, there is a change from 3004 in a form template's │ │ handling of OK buttons. The new template generates an │ │ undefined tag on the previous OK buttons. This is marked by │ │ (UNREFERENCED #EMBED) in the Embedded Source. This requires │ │ I export the code from the OK button processing and import │ │ it underthe current OK button processing. │ │ I believe that there were two code points for OK │ │ and Cancel in the 3004 templates. The real problem is that │ │ no error message is generated to indicate that the 3006 │ │ templates are not handling things the same way. There is an │ │ error indication but onlu if I go into the Source │ │ of the Form. Should be more visible. │ │ Now I have to go through every module in │ │ every APP to see if I have a problem. (Probably explains │ │ why some things don;t work OK (ha,ha) under 3006). │ │ [Similar problem with "BATCH" and │ │ (UNREFERENCE #EMBED)] │ │ R&D: This EMBED change has been in distribution through │ │ all of 3007.1. I hesitate to put the EMBED back because of │ │ a couple of problems, the least of which is that there │ │ really should NOT be two EMBEDs that do the same thing. │ │ Any users who this affected have fixed the problems by now, │ │ and we don't need to add new problems later down the line. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3318 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 12/15/93 │ │ Reported In : 3006 RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Btrieve currently does not support a 'manual' key. This is │ │ a key that if any component of the key is null an entry is │ │ not put in the key. Hopefully we can add this in a future │ │ release. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3326 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 12/15/93 │ │ Reported In : 3006 RevisedDate : 1/28/94 │ │ Fixed In : Status : Response │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Question from user: │ │ "I need to read the DS register, set the ES register equal │ │ to it, and then call INT86X with SREG initialized. How do I │ │ do this? │ │ Could I get an answer to this. I don't even know if it is a │ │ legitimate question. Thanks. │ │ Debby │ │ R&D: You can find the DS register by taking the segment │ │ part of the address of a variable global to a module. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3329 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 12/15/93 │ │ Reported In : 3006 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If a file is OPENed exclusively the autonumber code in the │ │ form template still generates a HOLD to the file. This │ │ would rarely cause problems (except in 3006 where there is │ │ a bug in the PUT / HOLD statements).... │ │ but... we shouldn't be issuing HOLDs in a single user app. │ │ It's confusing and just bad code. │ │ R&D: Now Generating HOLD only if Shared Files ON. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3338 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 12/16/93 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ graphics library -- in the demo example - the menu option │ │ named shades and icons -- │ │ when you get to the point where the super icons are and the │ │ animation of the super icons, the super icons are not │ │ displayed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3352 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 12/20/93 │ │ Reported In : 3006 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In driver.doc for the basic driver the following line is │ │ incorrect: res = SEND(ALWAYSQUOTE=OFF) │ │ it should be res = send(file,'ALWAYSQUOTE=OFF') │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3362 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 12/21/93 │ │ Reported In : 3006 RevisedDate : 2/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ if a pulldown menu is using the RIGHT attribute you cannot │ │ format the pulldown menu in the formatter │ │ R&D: RIGHT attribute is now supported and maintained in │ │ the pulldown formatter; however, the formatter does not │ │ display the item in proper WYSIWYG fashion at this time. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3363 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 12/21/93 │ │ Reported In : 3007b RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the folowing templates have hotletters being used more than │ │ once: │ │ browse : a e d l │ │ form : a n i │ │ pulldown: s │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3383 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 12/23/93 │ │ Reported In : 3007 RevisedDate : 3/07/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Print Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you are using the Print template, and you just put stuff │ │ in the Header section (nothing in the Detail section) the │ │ code to print the Detail section will still get generated. │ │ R&D: (Tom Moseley) The report formatter always forces one │ │ line for the body of the report. I'm not certain this is a │ │ bug. What do you think, Lisa? │ │ R & D(Lisa) In order to get a page header to print, some │ │ type of Detail structure must be printed since the report │ │ engine is responsible for printing headers/footers. If you │ │ do not wish to have a blank line printed you may either put │ │ a suppress on the detail or an overprint Next on the │ │ detail. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3391 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 12/23/93 │ │ Reported In : 3007b RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : REPORT ENGINE │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The option for printing a report acts odd. First of all │ │ the default report now has a formfeed in the footer. This │ │ is not necessary since more often than not I will provide │ │ my own form feed. The real problem comes where I send a │ │ one page report to the screen then print it. Three form │ │ feeds get entered. One from my report, one from the report │ │ structure in the default view proc, and one out of thin │ │ air. (pfm) To debug this, I placed a stop just before the │ │ close report. At that point, there was no form feed sent │ │ to the printer. but once you get through it I receive 3 │ │ form feeds. This in turn provides two blank sheets of │ │ paper. Where is this coming from. I used the orders.app │ │ customer report for an example. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3400 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 12/27/93 │ │ Reported In : 3006 RevisedDate : 2/01/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have tracked this to the SET(KEY,KEY,FILEPTR) in the │ │ RESETLAST routine. If you just do a SET(KEY,KEY) the │ │ problemdoes not occur. (Both servers are netware 386 with │ │ BTRIEVE.NLM, BSPXCOM.NLM and BROUTER.NLM Loaded. The │ │ workstation is using BREQUEST.EXE ver.6.01) │ │ I have discovered another problem related to using CDD on a │ │ network. If you have captured a port (non physical) other │ │ than LPT1 with the Novell CAPTURE utility and try to print │ │ are port to the selected logical port, you will get a │ │ message that the 'Printer is not on line'. Apparently, the │ │ STATUS command is accessing the hardware at the BIOS │ │ level and does not recognize that there is a valid logical │ │ port in existence. │ │ One More.. If in a single procedure, you have two reports │ │ opened simultaneously and redirected to a FILE, when you │ │ try to print a detail from the second report that was │ │ opened,itends up on the first report. This situation crops │ │ up when you have a primary report opened and you wish to │ │ print a LOGREPORT of the data from the first report. Call │ │ meif you have questions: │ │ Jim Grotjan 817-284-3208 │ │ User# 207934 │ │ cid 72451,75 │ │ proj 2867 │ │ SF2BC: I have fixed the Btrieve problem. I have passed │ │ this onto you for the STATUS bug report. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3401 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BZ DateReported : 12/27/93 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : 3007 Status : Tested/OK │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The creation of the Errorinf.$$$ file has no value to the │ │ enduser; they don't want to know what the codes are, just │ │ the text describing the error will do nicely. The best │ │ example is STACK OVERFLOW: instead of creating the │ │ ignominous Errorinf, we need to display a runtime halt │ │ window (ala 2.1), that states "STACK OVERFLOW". I attached │ │ some code to cause a stack overflow, I can do the same for │ │ Array index problems etc., ANY RUNTIME HALT should display │ │ a message, NOT just dump some codes to a file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3420 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 12/29/93 │ │ Reported In : 3006 RevisedDate : 2/03/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Erik Pepping 100135,472 MSG#:47723 │ │ I always get a crash when using chain in protected mode │ │ when I indicate a path in my .exe to chain. Try │ │ CHAIN(<path>\<exefilename>). This will crash. │ │ Erik Peping │ │ From Greg_W: I duplicated the Xtrace when I had an invalid │ │ path and linked in protected mode. Valid paths worked │ │ fine. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3423 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 12/30/93 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CSHELL Does not use the option that are set in │ │ CLAPRINTDEVICE. │ │ R&D: Since CSHELL is a standalone program as well as a part │ │ of the environment, it cannot. │ │ Tech: Then the help need the be changed to "...printing │ │ tasks you do thru the Clarion environment (except for │ │ CSHELL). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3440 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/03/94 │ │ Reported In : 3006 RevisedDate : 1/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Dave Cohen 70431,132 MSG#:48754 │ │ The popup window that reports hardware management problem, │ │ such as printer offline or invalid drive, has 'management' │ │ mispelled- 'Hardware Managment' (lost the 'E'). Nice to get │ │ an easy bug, huh? -dave cohen │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3446 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BZ DateReported : 1/03/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A "Locator" on a Descending order Browse will position to │ │ the record prior to the "correct" record in the KEY. │ │ R&D: This appears to be an artifact of the browse engine. │ │ I'm not certain this can be repaired by 3007 release. │ │ R&D: Repaired in 3007.2 Template Release. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3469 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/05/94 │ │ Reported In : 3006 RevisedDate : 2/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Scott Lowry 72322,2735 MSG#:47506 │ │ Yes, I did get your reply to my message of a month ago re │ │ Graphics Library problems. After more trials and errors, I │ │ think I can make this briefer than it would have been │ │ before. │ │ > you should only link in support for the graphics │ │ modes you use │ │ First, I think you're saying, and it appears to │ │ behave as though ALL graphic drivers that you're wanting to │ │ support get LOADED into conventional lower memory as soon │ │ as any graphics library procedure is called. That explains │ │ why the program ground to a halt after calling same, all of │ │ a sudden having 200K-300K less memory to operate in. If │ │ thisis true, it's a terrible step backward from 2.1 where │ │ you could link all drivers into the program, but load │ │ only the one you needed with the SETVIDEO(GETVIDEO()) │ │ statement. If there is something I can do to link all the │ │ drivers, but load only the one called for, please tell │ │ me how. For now I've dropped Hercules support, which I │ │ can probably get awaywith, but I must have CGA and EGA/VGA │ │ and loading both thesedrivers is taking up a lot of │ │ precious memory. (With thousands of users I don't │ │ have the luxury of "linking in support for the graphics │ │ mode you use"). Incidentally, sincedropping the Hercules │ │ support the program no longer goes into "crawl" mode, │ │ taking 7 seconds to load 50 records into a LIST box. (That │ │ problem occured in regular CDD non-graphicLIST box screens │ │ anytime after a procedure using the graphics lib had │ │ been called, even though one had RETURNed from that │ │ procedure). │ │ Second, │ │ the overlay manger seems to have a problem with │ │ procedures that use the graphic library, as the program (my │ │ app) will crash with an "out of memory" error on a very │ │ arbitrary and unpredictable basis when such are called. If │ │ Ireduce my memory by loading a TSR, then the problem │ │ becomes more frequent, and still unpredictable. There is no │ │ such problem on procs that don't use the graphic lib. │ │ Has this been reported as a bug? Is it being fixed? Is │ │ there a work-around? │ │ Third, there's a non-documented anomoly that │ │ creates an immediate System Halt crash if you try to do │ │ a 'Make and Run' when your project file has 1) the .OBJ │ │ stub that eliminates Hercules support (probably any │ │ .OBJ) placed before the CLA files, and 2) the 'pack' │ │ link option is 'Off', and 3) the debugger option is │ │ not being called. It took several hours to run that down, │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3490 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/10/94 │ │ Reported In : 3006 RevisedDate : 3/01/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Scott Merritt 71140,2502 MSG#:49353 │ │ This message is regarding a problem I am having with the │ │ "v" picture element. I have incorporated your changes but │ │ there is still a problem when I am dealing with a number │ │ less than 1. │ │ Example file: 3490.zip │ │ DH: This is a dup of 3482 - please see that bug as it │ │ hastwo example files. Thanks │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3492 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/11/94 │ │ Reported In : RevisedDate : 2/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the Add Ons section of the Make system, IF one addon has │ │ an error we do not get any of the ones that were sucessful. │ │ This slows the testing of fixes down. │ │ It would be nice that if an Add On was successful that it │ │ was moved to it's proper location. Then allow the next one │ │ to be made. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3494 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/11/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ get(queue,key) on a valid key value return e30 entry not │ │ found. see 3494.zip │ │ R&D:The "Fieldness" of a Que field can not be passed as a │ │ parameter. When a que field is passed it becomes a normal │ │ string, or long or real, then when you think you are using │ │ it as a key like GET(Que,+KeyField) you are really │ │ converting it to a number and calling GET(Que,Pointer). To │ │ pass que fields you must use the NAME attribute on the │ │ field and pass the name specified in the NAME attrubute for │ │ that field as a string then when you say GET(Que,'Myfield') │ │ it will find the field in Que with a NAME('Myfield') │ │ attribute and use it as the key. RTFM(NAME attribute) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3600 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/25/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Report Writer │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the Report Formatter (Report Writer, App Gen, & │ │ Editor)... │ │ When Use Rulers is on (ctrl+R) and you move the cursor to a │ │ new spot with a mouse click.... │ │ The "old" ruler stays where it was. If you use a cursor │ │ key to move the cursor or press enter to open a line, a │ │ "new" copy of the ruler appears. If you repeat this, you │ │ canhave 5 or 6 "copies" of rulers on a screen. │ │ When you move the cursor over the "ghost" rulers, │ │ they disappear. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3497 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/11/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the Report Properties window, the entry field for Lines │ │ per Page only accepts two characters. │ │ If using a printer that can print 8 cpi and using legal │ │ sizepaper (8.5 x 14in) , the lines needed would exceed 99. │ │ (even with a half inch margin on top and bottom) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3498 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 1/11/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Not a big thing, but..... │ │ In the Report Properties window, the prompt for "Printed │ │ lines per page" has the letter R as the hot letter. Alt-R, │ │ however, always opens the pulldown menu "Report" drop box. │ │ The Hot letter needs to be modified. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3500 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/11/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ erase does not erase a use variable in a string structure │ │ correctly. see 3500.zip │ │ f1 will erase the use for the string option and then show │ │ it │ │ f2 will erase the use for a radio button option and then │ │ show it │ │ f3 will show the use for the string option │ │ f4 will show the use for the radion option │ │ QA&E: Where is the Zip File????? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3501 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/11/94 │ │ Reported In : 3006 RevisedDate : 3/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Silver 74145,1546 MSG#:49597 │ │ I am not certain if this has been reported but since I do a │ │ lot of hand codeing I come up with these things. The │ │ following code gives a different answer when compiled in │ │ 2.1 and 3. │ │ TEST PROGRAM │ │ TRL_START STRING(5) S_NUM │ │ SHORT │ │ code │ │ TRL_START =1010 │ │ TRL_START=(LEFT(TRL_START)) │ │ S_NUM=INSTRING(' ',TRL_START)-1 │ │ TRL_START='$' & ALL('0',4- S_NUM) & TRL_START │ │ SHOW(25,1,TRL_START) │ │ ASK │ │ In 2.1 the trl_start becomes $1010 and in 3006 │ │ it is $0000. The reason is that the all('0',0) is │ │ interpreted differnetly in the two versions. Please refer │ │ to R&D. David Silver │ │ R&D: Requires minor compiler changes; sent to London, will │ │ be available in future release. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3503 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/12/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Paradox Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Enclose example will not read the paradox file. If you │ │ delete the existing datafile,add the create attribute;no │ │ records will display in the browse. If you try to look at │ │ the file with the database manager you will xtrace. If you │ │ are running the program and do alt= for system info; select │ │ files; you'll xtrace. │ │ File is "as is" from user. PDXREC indicates a different │ │ label for the key. I tried changing this with no effect. │ │ I added a form to the browse to add records. no effect. │ │ My changes are not included. │ │ clarionet upload │ │ userid jhawe │ │ proj 2750 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3504 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BZ DateReported : 1/12/94 │ │ Reported In : 3007 RevisedDate : 2/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The INLIST() function fails compilation if called with only │ │ one list parameter i.e. S# = INLIST(Srch,List) will fail │ │ with compiler error "wrong number of parameters". │ │ QA: Is this a documentation error? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3505 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/12/94 │ │ Reported In : 3007 RevisedDate : 2/28/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When I try to compile a paradox program I get the warning │ │ about transaction frame. After generation the Cancel button │ │ is highlighted. If I press enter on Cancel, the program │ │ compiles anyway. Also what is the deal with this template │ │ warning. It lets me know that I can't do a logout. With no │ │ shared files and no constriants, why would I be doing a │ │ logout anyway. The message indicates that I should read │ │ template help. Will this warning always display. Template │ │ help doesn't tell me to do anything to not get the error? │ │ See file 3505.zip │ │ QA&E: To get rid of the Warning, turn of Template Warnings │ │ before generating code in the Project Options Dialog. │ │ Debby: WRONG ANSWER <g> Why should I get a warning at all. │ │ The code doesn't generate a LOGOUT at all. The template │ │ error should be conditional. I should not have to turn off │ │ template warnings for a warning that I shouldn't get in the │ │ first place. │ │ How about the Cancel button. Should that be logged as │ │ another error? │ │ R&D: This warning is generated because the Paradox driver │ │ does not support LOGOUT. The reason we do a LOGOUT even if │ │ a single user program is to protect the data from │ │ black-outs, surges, etc. Use the "Disable RI Logout" check │ │ box to prevent this warning from appearing. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3506 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 1/12/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Problems with loading a file which has over 64k of records. │ │ Screen scrolls improper information and search doesn't │ │ work. │ │ R & D - Now stops you at 65535 records and asks you if you │ │ want to continue or abort │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3507 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 1/12/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you are loading a file in the editor and end up running │ │ out of disk space (from swapping) you get an error like │ │ disk full, then xtrace. The space taken up during this │ │ file loading process is eaten from your drive and no │ │ temporary or swap file can be found. A CHKDSK /F will │ │ indicate lost sectors and free up the lost disk space. │ │ R & D - I was able to reproduce the disk full error message │ │ however I did not xtrace. Anyway I was also able to free up │ │ lost disk space with a chkdsk/f. This is not an editor bug │ │ but either a Loader or Library bug! │ │ R&D:This is not a bug! The extender has to halt immediately │ │ if it runs out of disk. If you get a report like an XTRACE │ │ you are priviliged. We are making good progress with │ │ quantum memory, but in the mean time, out of memory means │ │ ByeBye! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3510 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/12/94 │ │ Reported In : 3006 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: DOUG ANDREWS 73740,2622 MSG#:49781 │ │ program │ │ num decimal(10,0) !happens with Decimal(11,0) also. │ │ code │ │ num = 9876543210 │ │ t" = format(num,@n_10) │ │ ask │ │ When I run this code (using 3006), I get a floating point │ │ error. The error occurs when the format is executed. If │ │ you change the format token to @n_11, it works OK. │ │ I tried it in both protect mode and dynalink. │ │ Thanks Doug Andrews │ │ R&D:Doug this is a result of the compiler optimizing the │ │ code generated so that you don't have to use temporary │ │ floats for all internal calculations (which would slow your │ │ program to a crawl). When the compiler sees @n_10 it │ │ takes a chance that the number will fit in a long (much │ │ faster than float). Unfortunately even an unsigned long │ │ will only fit 4294967296. Consequently, when the │ │ conversion function in FORMAT tries to store it in the │ │ temp. long it causes an overflow exception to indicate that │ │ the number can not be represented. The @n11 works because │ │ the compiler knows full well an 11 digit decimal can never │ │ be represented by a long, and so full float arithmetic is │ │ used. You might say the compiler should not assume that an │ │ arbitrary 10digit number will fit into a long, we will take │ │ this under advisement. Thank you. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3511 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/12/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Report Writer │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When using Multi Up Columns... │ │ Although a Two Up Report prints just fine to CON, when │ │ printing to printer or a file it sends a CR/LF after each │ │ field on a line. │ │ Instead of: │ │ Rec1Field1 Rec2Field1 │ │ Rec1Field2 Rec2Field2 │ │ We get: │ │ Rec1Field1 │ │ Rec2Field1 │ │ Rec1Field2 │ │ Rec2Field2 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3515 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/12/94 │ │ Reported In : 3007b RevisedDate : 1/26/94 │ │ Fixed In : 3007 Status : Tested/OK │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The project monitor window is returning warning with │ │ dlst.cla in all models. If the dlst.cla program is │ │ compiled and run from the environment, it will return, │ │ 'cannot execute program'. If DLST.EXE is run from the DOS │ │ prompt it runs properly. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3518 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/13/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When you Save As, instead of changing to the new .RWF, it │ │ remains in the original. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3519 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/13/94 │ │ Reported In : 3006 RevisedDate : 2/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The show statemend doe not require a row and col attribute │ │ according to the docs. If you don't include the row, col │ │ then nothing will print. No compile errors just doesn't │ │ print anything. See file 3519 │ │ digital solutions │ │ proj 2923 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3520 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/13/94 │ │ Reported In : 3007 RevisedDate : 3/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the graphics library demo program (demo.cla) has the │ │ following problems in protected mode with or without run │ │ time libraries, under os2: │ │ 1. Bar Graph Styles option - processor violation, xtrace │ │ 2. Fonts - super text character sets, cannot use up/dn │ │ arrow to scroll through fonts │ │ 3. Interactive graphing - upon return from graph you get a │ │ runtime halt, no open screen │ │ 4. Menus and Editing - processor violation, xtrace │ │ 5. Pie charts Pallette - shows lines all over the screen, │ │ not a pie chart. │ │ 6. Polar Graphs - processor violation, xtrace │ │ 7. Polylines and vectors - locks up │ │ 8. Shade and icon library - shows icons all over the screen │ │ 9. simple xy example and code - processor violation, xtrace │ │ 10. Statistics functions - processor violation, xtrace │ │ 11. Various graphs and charts - processor violation, xtrace │ │ 12. XY graphs and styles - processor violation │ │ BC: Working on it.... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3521 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/13/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in protected mode without run time libraries you get the │ │ following two compiler warnings: │ │ _dgemaincgm is duplicated │ │ _dgemainhrc is duplicated │ │ R&D: Compiling the demo program VIEWS.CLA does not produce │ │ this. Are you certain you are not linking the library │ │ twice? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3522 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/13/94 │ │ Reported In : 3006 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick Weiss 71764,1312 MSG#:50013 │ │ This is a report of a minor bug in the polldown template in │ │ 3006. │ │ If you select menu option X, and procedure X (called from │ │ menu option X) does a DISABLE(?X), a sticky menu will leave │ │ "X" selected and an ENTER key will still call procedure X │ │ even though it is disabled (greyed). │ │ I'm sure you have one or two more serious problems, but │ │ I thought I'd pass it along. │ │ R&D: Fixed in version prior to 3007. Appears to have been │ │ PullDown structure bug, fixed for 3007. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3525 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/17/94 │ │ Reported In : 3007 RevisedDate : 1/25/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ From the Report Worksheet.... │ │ If you change to 43/50 display, the worksheet title and │ │ part of the border vanish. They are still gone if you │ │ change back. │ │ I tried this on both EGA and VGA monitors, with the same │ │ results. Also did not happen on other worksheets (Procedure │ │ worksheet, Data Dictionary worksheet, etc.) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3529 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/17/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In cshell, a sort by time give very strange results. Seems │ │ that anything after 4pm will sort at the top of the file │ │ followed by the correct sort starting at the beginning of │ │ the day. │ │ R&D: Strange one...fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3532 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/17/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the setpath() statement will return a path not found error │ │ if the path you are changing to contains an ending │ │ backslash. │ │ ex. setpath('c:\data\') │ │ this is used in the file template. a backslash is appended │ │ onto the current path in the beginning of the file template │ │ and at the end of the procedure a setpath() is done to │ │ change back to the starting directory. │ │ R&D:Fixed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3535 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 1/17/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you tag a single file, then flip tags and delete all │ │ other files, the single file not tagged will not be │ │ displayed unless you force a directory update │ │ R&D: Can't dup over here. Need more info. │ │ Follow up: I duped it in Mike's office a couple of weeks │ │ ago. Mike is aware of this problem.... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3537 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/18/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ For a memo the ins attribute is ignored. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3538 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/18/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you do a restart in an idle procedure, you can no longer │ │ arm the idle procedure. see example file │ │ Cindy Cohen │ │ cs id 71477,3013 │ │ proj 2941 │ │ R&D:Dearest Cindy, I think I would really hate pulling │ │ maint. on this package:) Anyway, we're not going to add │ │ this functionallity (too bizzarre) but I think I have a │ │ workaround. In the loop where you wait for keys comming │ │ back out of ASK, dissarm the idle. That is; dissarm the │ │ idle when you have returned from ASK, ie: when you detect │ │ the Alt-J might be a good time. Then you can do the │ │ restart safely. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3541 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/18/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Once you are in the list box formatter, left mouse click on │ │ the first row of the screen. You will see the normal │ │ pulldown with magenta border. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3545 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/18/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ there is no help in the template help for the 'Keep │ │ pulldown active' prompt on the pulldown template │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3546 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/18/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ From Todd Seidel: │ │ Using a SKIP(file,-n) where n takes you before the │ │ beginning of the file, BOF() will not be properly set. │ │ I have requested a test file from the user. │ │ R&D: The SKIP test in the driver suite shows this working │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3548 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/18/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Example Applications │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in the ebrowse example the procedure br_names_locator is │ │ using the code_key key and doing a locator on name. │ │ Code_key is on based on the code and name fields. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3552 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ IsAValidDrive() which is defined in getdir.inc is not │ │ included in the api docs. it should be included in │ │ both.inc and cla_lib.inc │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3554 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like the ship list to include the styles file if │ │ the app will be using one │ │ QA&E: The ship list is getting its infomation from the │ │ PROJECT System not the CLAs. It would be ridiculous to │ │ expect it to read thru ALL of your CLAs to find everything │ │ you may or may not need to ship. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3555 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like to suggest that the changes.doc file be │ │ renamed to chang06.doc, change07.doc so the old changes.doc │ │ file does not get overidden with the new one. │ │ QA&E: Can't you people make up your MINDS???? I suppose │ │ you want your cake and Edith too! │ │ We have not done this in the past and I doubt it will │ │ happen in the future. │ │ We suggest that the user backup ALL volitile files prior to │ │ Install/Patch! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3558 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Right now you cannot move a menu from the left to the far │ │ right on the action bar. Could you allow this, please? The │ │ workaround is to move the menu to next to last then move │ │ the far right to the left one slot. │ │ R&D: Implemented new move paradigm - CtrlM now immediately │ │ moves the highlighted item one position to the right (or │ │ down if in a menu box). The item will wrap to the │ │ beginning if it is on the end. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3560 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Ctrl-home clears the entire field's contents regaurdless of │ │ cursor position. I have never seen documented what this │ │ was supposed to do but I heard a rumor one day. │ │ R&D: Works like this in 2.1. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3564 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After pulling up the Ruler, ctrl-R, if you mouse click on │ │ the ruler let's say on a number then that number will end │ │ up on the screen itself. Not permenantly but it looks │ │ strange. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3568 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : View Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you choose to use the print option on the view template, │ │ and your report in wider that 80 columns, everything after │ │ column 80 will be truncated. │ │ R&D: Not a Bug. This is the way that CLARION.APP is set │ │ up, and the user can change our settings by changing either │ │ CLARION.APP for all VIEWs, or in the VIEW in question by │ │ changin the REPORT attached to the VIEW procedure. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3569 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Print Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ line 63 needs to have clip thrown around it or you will not │ │ find the file when it goes to screen. │ │ ? why isn't the code exactly the same for this section of │ │ code as the report template? Regaurdless of the size of │ │ thereport shouldn't the code be the same to send the │ │ report someplace. │ │ R&D: Fixed in Template Release 3007.101 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3570 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The File Template is changing directories after selecting a │ │ file in a directory different from the program directory. │ │ This can be a disaster if you are in a Form procedure with │ │ a record in memory. Clarion attempts to update the record │ │ to the different directory and returns a variety of file │ │ I/O errors. Current workaround is to use the SETPATH │ │ statement at the end of the procedure. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3572 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the prototype is incorect for qshow-- │ │ The api_3.txt has the correct prototype. │ │ instead of *? it should have *string and add the raw │ │ attribute. │ │ R&D:Fixed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3574 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/22/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is my understanding that if you have a monochrome VGA │ │ that we will still detect the hardware as color and use the │ │ color codes for color monotors from the styles file and not │ │ the mono colors. Is it possible to change this or give the │ │ user the ability to force the specific graphic mode. │ │ R&D: Try MODE BW80 to get mono styles. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3576 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/22/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : ASCII Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Batch 3006. Using file driver 'Ascii', compiling in 'exe' │ │ with overlays, you │ │ can bomb the system using 'add (file, length)'. Example: │ │ File file, driver ('ascii'), name ('dfile.log') │ │ record │ │ Txt string (80) │ │ end │ │ end │ │ code │ │ create (DFile) │ │ open (DFile) │ │ Txt = something... │ │ add (DFile, len(clip(Txt))) │ │ Scott │ │ I know this is redundant code but it probably shouldn't │ │ bomb. See test file 2576.zip │ │ DH │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3577 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ ErrorFile is not returning the file name. This does work │ │ for the Btrieve Driver. See the test file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3578 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/27/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : VGA Color Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ With the install set that I have for tools, the spectrum │ │ exe was made using the extender. Since I do not have the │ │ extender it xtraced. I was able to create a new exe after │ │ changing the project file. In a future install set we │ │ should ensure that we do not send out something that │ │ requires the extender to prevent confusion. │ │ R&D: SPECTRUM.EXE should now ship as an OVERLAY program. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3579 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/27/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the screen formatter create a virtual screen 25x210. │ │ Now try to place a repeat structure (scroll/repeat) 5x210. │ │ The repeat structure will go from left border to the right │ │ border. When you try to save the screen you will xtrace │ │ ts proj 2850 │ │ QA&E: Pam, where is the test file????? │ │ Can not create a test file because it xtraces when you try │ │ to save the screen! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3580 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/25/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ xtrace occurs in the database manager in key order after │ │ a few records are displayed; works ok in record order │ │ R&D: Need demo │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3581 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I thought the purpose of Record Picture vs Display Picture │ │ for a string field in the dictionary editor was how the │ │ string was declared. Where the REcord Picture declared the │ │ string │ │ var1 string(@picture) │ │ and a display picture simply declared the string lenght. │ │ var2 string(10) │ │ It is really not too important unless someone declares a │ │ string lenght of 9 with a display picture of @d1. │ │ They will get invalid record declaration if they try to │ │ read it with the dictionary editor, but their program will │ │ read the data file. This is because the code is written as │ │ var string(@d1) which is actually a string(8) │ │ My point ????? │ │ The display picture should not have any effect on the │ │ declaration. Yea or Ney ?? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3582 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CSHELL will XTRACE under the following circumstances. │ │ 1. Have a Directory that is more than 1pg of files. │ │ 2. CTRL Space to TAG all files. │ │ 3. Go to the last file listed and UNTAG IT w/ CtrlT │ │ 4. Press DEL to delete all the Tagged Files. │ │ 5. When it is done there are no files in the List. So I │ │ pressed UpArrow and BOOOM! C YA WOULDN'T WANTA BE YA! │ │ R&D: Fixed, but it may be a few days before you see the │ │ fix, since we are in this 3007.1 limbo. It will be in 3008. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3585 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/25/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ BAD NEWS - while in screen design in browse, select etc. │ │ the function of the end key has changed to the end of the │ │ screen not the end of data, VERY NASTY until you get used │ │ toit, WANT IT BACK TO THE END OF DATA NOT THE END OF SCREEN. │ │ Example: the title of a browse screen, 3006 type the │ │ title, CTRL_6 (center) Home (left start of title), CTRL_M to │ │ move, END to the end of title, Move the field up, done Now, │ │ singlespace to the end of the title before pressing enter │ │ on the field. │ │ R&D: This was done BY REQUEST to make the end key │ │ consistent in various functionality. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3584 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ INT does not just drop the Decimal places, it is Rounding │ │ the variable. See test file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3586 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/24/94 │ │ Reported In : RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Database Browser │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the Browser, from the Column > Header > submenu... │ │ Pressing F1 with any of the first four options highlighted │ │ results in Help Error window. │ │ "Help ID 'DTBPDHEADER' not found in CLARION3.HLP" │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3587 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I believe this is known to R&D but I wanted to log this. │ │ Real data types assigned to Interger data types, │ │ round instead of truncate │ │ int(12.6) will return 13 │ │ and real = 12.6 │ │ long = real │ │ long will equal 13 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3588 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Btrieve driver does not like the SKIP(file,+-n). It │ │ also does not work in the CLarion Driver as expected. │ │ See test file from user. │ │ R&D: There is a bug in the users test program. He is │ │ doing SKIP(file,1) instead of SKIP(file,-1) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3589 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I suggest we increase the size of REPORTDEVICE. Currently │ │ it is a string(30). The filename takes half of this and │ │ does not leave much room if current directory is nestled │ │ within some subdirectories. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3590 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ take a look at the enclosed example. there is a problem │ │ with the range limits on a validate procedure. i am │ │ priming the key field on the entry field from the form. │ │ when the validate comes up, there are no records showing. │ │ the sav:: field is not getting saved properly, so when the │ │ key field is primed with the sav:: field it is really │ │ getting cleared out. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3591 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When on a screen, and pressing an un-alerted ALT-Character │ │ (for instance, ALT-Q on this screen), the character value │ │ is entered into the current field. To demo this, select │ │ the first field above, and press ALT-Q. the T in TM will │ │ be replaced with a Q. │ │ QA Note: Try Ctrl-F or anything else for that matter. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3592 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is impossible to assign a different background color to │ │ the text in the header portion of a window drawn with │ │ borders on. I thought that in the past the color of the │ │ text was used to paint the heading. │ │ R&D: Nope. Can't work that way...never has, never will... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3593 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When you select to change the color of anything, and on the │ │ color screen press ALT-E to toggle enhanced / non-enhanced, │ │ the left and right arrows become inactive until you press │ │ the up or down arrows. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3594 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When using a window with an enhance white background, it is │ │ impossible to get a list box to display correctly. If the │ │ background of the list box is not enhanced white, the │ │ graphics displayed extend beyond the list box. If the │ │ background of the list box is enhanced white, the lower │ │ border of the list box disappears, because it is also │ │ enhanced white. │ │ R&D: You really shouldn't use bright white list boxes. │ │ Since there is no color _brighter_ than bright white, you │ │ get the appearance of a stretched list box since it's outer │ │ border is also bright white. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3595 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ SETPATH() does not work if the last character of the passed │ │ parameter is a backslash. For instance, │ │ SETPATH('C:\CLARION3') works, while SETPATH('C:\CLARION3\') │ │ does not. Either should work the same. │ │ R&D:Same as 3532 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3596 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RUN() when using a string variable (with only 40 characters │ │ in the string) will fail the second time through. The │ │ method of failure is that the machine locks up tighter │ │ than... well, it locks up. If you CLIP() the variable it │ │ works fine. │ │ R&D:Could not reproduce │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3597 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ On a browse with incremental locator, tab from the locator │ │ to the Change button, then press the up or down arrow, and │ │ the first field of the first ListBox entry is ... GONE │ │ You can see for yourself in the EBROWSE incremental locator │ │ R&D: Fixed in 3007.100 patch (fix to BROWSE.CLA) │ │ Fix improved in 3007.101 template release │ │ (3007.100 fix re-read record when tabbing between │ │ fields) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3598 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/25/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Editing an error on generated code works fine until you try │ │ to save the changes. In the window that pops up the entry │ │ field for the filename is blank, if you press OK to get out │ │ of the edit errors screen, a warning pops up telling you │ │ 'path not found' │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3601 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/25/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in the template help for the global settings the new source │ │ embed "Before File Declaration" is not documented. It would │ │ be also good to have a description as to why you would use │ │ one vs the other "data section" vs "before file │ │ declaration" │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3602 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/25/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 2. When I perfoem a CHAIN(Programline) their is something │ │ wrong with using the command('string',3) function. The │ │ command line from the chained program is not read │ │ correctly. │ │ Example. Chain ('TEST CLAINI=A.INI GEB=SYSTEM │ │ PASS=ABCD') when using Command('CLAINI',stirng) in TEST │ │ the result is the full string after CLAINI. The spaces │ │ are not seen. when starting from dos it works OK ! │ │ R&D:Fun bug, couldn't use the debugger... fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3603 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : DBase III Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Adding three records to the program and then simulating a │ │ crash (re-boot or reset) none of the records will be saved │ │ and I end up w/ lost allocation units on my HD. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3607 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/27/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the file 3607.zip, there is a procedure named │ │ ScheduleScreen. Under the files pushbutton there are no │ │ files in the file skematic. However, the schedule file was │ │ at one time. Problem is that the code for opening the file │ │ is still being generated by the template. │ │ R&D: When an orphan file existed under a procedures' File │ │ button without any files defined in the file schematic it │ │ was improperly "promoted" to the primary file. │ │ The use of orphan files is currently not well-defined. This │ │ will be addressed in 3.1 by the addition of a %OrphanFiles │ │ symbol to enable access to those files in the templates. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3606 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 3/01/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ sreal set = .01 will display as 0.00 with a │ │ show(1,1,sreal,@n7.2) │ │ see file 3606.zip │ │ I gave this directly to BobZ in case it might have │ │ something to do with the INT bug. │ │ User reports that it happens in 3006 also. │ │ R&D:0.01 can not be represented in binary. The actual │ │ value store in the FPP is 0.009999999. Now all the │ │ calculations in the internal library are done in high │ │ precesion REALs. When the SREAL is translated to a REAL │ │ you get 0.00999999943527, where the last five decimal │ │ digits are left over garbage. Now when this value is │ │ rounded for display the high digit is bumped by 5 yielding │ │ 0.00999999943532 and then truncated to the desired │ │ precision. If you are intent on using SREALs for I/O you │ │ can manually force the value up by adding 0.000000005 │ │ causing the value in the REAL to be 0.01000000043527. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3608 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PS DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Tested/OK │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fill a memory queue by key. Now Clear the field and do a │ │ GET(Q,KEY). Since I know there are no blank elements in │ │ thequeue I should get an errorcode 30 "Entry Not Found". │ │ This is not happening. │ │ R & D : Blank elkements are now returning an errorcode. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3609 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the following code never gets to the second record in the │ │ file, it falls into an infinate loop. │ │ SET(Con:ContactNoKey) │ │ StatusString = CENTER('Changing Records',LEN(StatusString)) │ │ DISPLAY │ │ LOOP │ │ NEXT(Contacts) │ │ EMBED('~~btch~1~NEXT Record Error Check~5~~') │ │ IF ERRORCODE() THEN BREAK. │ │ ENDEMBED │ │ EMBED('~~btch~1~Within LOOP~5~~') │ │ con:state = 'NJ' │ │ ENDEMBED │ │ PUT(Contacts) │ │ EMBED('~~btch~1~PUT/DELETE Record Error Check~5~~') │ │ IF ERRORCODE() THEN STOP(ERROR()). │ │ ENDEMBED │ │ END │ │ to workaround you need to place another next statement │ │ after the put() and errorcode() checking. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3610 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Image fields are causing memory reduction and eventually │ │ the program will run out of memory. This is happening in │ │ the Static model. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3611 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When I select protected mode, the only target │ │ hardware 3007 allows me to optimize for is 80286. If I │ │ select 80386 or 80486 or │ │ Math Coprocessor, it will not save these selections nor │ │ will they be reflected │ │ in the project file. 3006 allowed me to do all of the │ │ above. │ │ R&D:When you generate Extender programs, you are using a 16 │ │ bit extender ie:286 code. That is; YOU ARE IN 286 MODE! │ │ not 8088 code, and not 386 code and not 486 code. In real │ │ mode there are some instructions that can be used to │ │ optimize the program without switching to protected mode │ │ this is why the other cpu options are available here. │ │ Scott says to put this back as a bug. He talked to BC on │ │ this. DH │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3612 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Example Applications │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the Ebrowse example the EntryOnRangeValue browse shows a │ │ procedure call to Browse_Codes which is doesn't make. In │ │ other words, it is entered in the Procedures button, but │ │ no code actually calls it. │ │ This entry field should probably do a lookup to the codes │ │ file. If so the entry field would be from the names file; │ │ range limit nam:code, no range value, call the browse on │ │ the when field is completed. This example is what alot of │ │ users want to do. I'm not sure what you were trying to show │ │ in this procedure │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3613 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When creating a new .RWF, if you type in a Dictionary │ │ File that does not exist (Report Definition Properties) │ │ it will XTRACE. │ │ If you press enter with the field blank, it brings up a │ │ picklist. │ │ With an existing .RWF, if you try to change the .DCT │ │ filename to a file that doesn't exist, it just reports │ │ and Error 012 File Not Found, a pick list comes up, and you │ │ can continue. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3614 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 51560 S8/3.0 Support │ │ 24-Jan-94 19:07:15 │ │ Sb: #Template Changes │ │ Fm: Advantage Software 100116,3350 │ │ To: sysop │ │ L.S. │ │ we have found the following anomality with CDD 3.007 │ │ It is maybe not a real bug, probaly more a matter of │ │ diffent interpretation. It can be quite supprisingly, │ │ however, to say the least. │ │ When the template of a procedure is changed, the │ │ properties │ │ of the procedure that are no longer used, seem to remain │ │ stored somewhere. The problem is, they are obviously │ │ still │ │ accessible by the code generator. │ │ For example, define a Validate procedure, and fill in the │ │ Display key field. This will set the %DisplayKey symbol. │ │ Now change the procedure template to Browse. As the │ │ Browse │ │ template has no Display key property, this is no longer │ │ visible. When you define a locator for the browse, │ │ however, │ │ a template warning will result. The code generator │ │ assumes │ │ %DisplayKey is defined, and requires the locator field to │ │ be │ │ part of this key. │ │ R&D: During a change of template we try and preserve as │ │ much data as possible to enable reconversion in the event │ │ the user needs to change back to the original template (ie. │ │ embedded source, screens, reports, pulldowns are all │ │ saved...). Prompt values are retained unless they conflict │ │ with a prompt type in the new template. I feel this is the │ │ safe conversion solution as opposed to running the risk │ │ of 'deleting' information. The user has a resolution to │ │ the existing problem where as once the information is │ │ deleted... ! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3617 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ USER REPORTS -- IN GUI -- Trying to Use row() and he always │ │ gets 18 vs when it is gui-less, it is returning the correct │ │ value. -=- a button with no text ie('') is acting one way │ │ while gui-less then when running with gui he xtraces │ │ R&D: Tried this and seems to work fine. Please send demo │ │ file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3616 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : 1/26/94 │ │ Fixed In : Status : Question │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have some questions regarding colors in Graphics Mode │ │ (using │ │ SetGraphic(89) or SetGraphic(87)). I have a SVGA color │ │ monitor capable of │ │ displaying 256 colors. Yet I note that setting my monitor │ │ to SVGA graphics mode │ │ causes me to lose my RGB color values that I set with │ │ SPECTRUM and the CLR file │ │ (I assume that works only in Text (90) mode). How do I (or │ │ can I) use more than │ │ the standard 16 colors in the higher Graphics mode? Also, I │ │ notice that setting │ │ graphics to 87 (SVGA) causes the screen to be compressed │ │ vertically │ │ slightly...IOW, the bottom few lines are blank on the │ │ monitor. How do I get │ │ HiRes Graphics to use the full screen AND access all │ │ colors? As you can tell, I │ │ know very little about SVGA graphics in the first place. I │ │ know this can be │ │ done, since other applications I run (WordPerfect for DOS, │ │ Windows, etc.) use │ │ the full screen, and also allows access to the full color │ │ range of the monitor. │ │ How do I write similar apps. in Clarion to take advantage │ │ of my monitors │ │ capabilities? │ │ I need help with this question. Thanks │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3618 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 1/27/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user suggests: │ │ in a source templates local data section, you should be │ │ able overlay a local field variable on a data file field. │ │ For example, in the local data section you have defined a │ │ BYTE field and you want to overlay over a another BYTE │ │ fielddefined in the local data section a procedure but │ │ clarion won't let you do it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3619 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ use the dat file from 3619.zip. before issuing a pack() on │ │ the file there are 466 active records and 57731 deleted │ │ records. after the pack() is complete there are only 316 │ │ active records. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3620 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you alert the Dos Command Line (either by alt+c or a │ │ mouse click) and then type in a command, and press enter. │ │ Command does't execute and the files listbox gets │ │ highlighted. │ │ If you type in a command without first alerting the Dos │ │ command line, it works fine. │ │ R&D: Fixed for 3008 make (could be a few days). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3621 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When creating a macro it is very difficult to record the │ │ keystrokes to copy a line or move a line. It seems you have │ │ to hit CtrlC twice and Enter twice. You also loose the │ │ message at line 25 that indicates you are recording. It │ │ will finally save. │ │ When you go to create a macro and you choose a key that │ │ already has a macro defined there is no warning. │ │ R & D - One comment about this. Because there is no way for │ │ me to know keystrokes after a dialog is chosen,those │ │ keystrokes will not be recorded in a macro. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3622 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : CPD 21 Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Actually form21 template. │ │ Sb: 3.007 Problems (*sigh* │ │ Fm: Tom Hebenstreit 72154,731 │ │ To: Debby Herman 72662,475 │ │ Form21 TPX BUG - Cancel button logic: There is a template │ │ IF/ELSE/ENDIF containing two possible actions, each │ │ containing a Clarion IF. Following that is a Clarion │ │ Elseto go with the IF statements. PROBLEM: the first │ │ Clarion if has and END statement in it which │ │ terminates the Case Keycode() and LOOP prematurely │ │ since the Else becomes a │ │ Case/Else, etc. WORKAROUND: Comment the END │ │ out (in the TPX) and it │ │ works as expected. │ │ R&D: I believe this is fixed in the 3007.2 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3623 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 2) Form21 TPX BUG - Autoincrement Add/Cancel leave empty │ │ Held record. │ │ I KNOW this was supposed to be fixed and indeed the │ │ template has code │ │ to fix it BUT it is not included in the generated │ │ code. I am not a │ │ template wiz, but from comparing it to the standard │ │ Form it looks like │ │ the TPX conditional IF(%AutoInc,...) is testing for │ │ "TRUE" in some │ │ places and "Y" in others, so some code that SHOULD be │ │ included is not. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3624 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3) Browse w/incremental Locator, Hot records/display fields │ │ At first I thought: great, no more first and last hot │ │ field stuff. │ │ But NOOOO, it seems it was replaced by a │ │ DISPLAY(?List,Fields()) which │ │ redisplays the Entry/Locator each time a key is │ │ pressed. This causes │ │ the locator to flash with the new records data (as an │ │ entry field) │ │ before being cleared (as the Locator) on every │ │ keypress. VERY ANNOYING! │ │ How do we get around this since the Locator must be │ │ after the List? │ │ R&D: Fixed in 3007.102 Template Release (Now displays... │ │ 1 to List-1, List+1 to Locator-1, Locator+1 to Last) │ │ Of course, only those DISPLAYs applicable are applied │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3625 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 2. Total Fields in BROWSE can't sum on formula fields. │ │ R&D: Fixed in 3009 template release │ │ 4. The incremental locator option should be dimmed if no │ │ locator field. │ │ R&D: Not a bug, dimming of options not allowed in current │ │ template language (3100 planned feature) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3626 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 5. In a conditional formula, if you want to clear a field │ │ by placing a numeric │ │ 0 in the field for the FALSE condition, it allows you to │ │ place the zero but the │ │ code isn't generated in the source code. Using a text '0' │ │ does work. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3627 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Report Writer │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you take a STRING field that has been made into a TEXT │ │ field and try to change it back, it will XTRACE. │ │ I know you can just delete the field & place it again, │ │ instead ok trying to change it. But, perhaps we can trap │ │ theerror before the XTRACE. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3628 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 1/27/94 │ │ Reported In : 3006 RevisedDate : 1/27/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry Smith 73072,3314 MSG#:52163 │ │ The big question. Why doesn't Clarion have a smoother │ │ upgrade path? A document saying "watch for these things │ │ whenyou move to 3007" would have made life easier. Also, say │ │ "this is like this now because ..." Agggh. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3629 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user -- when using a range for a field, under │ │ validity checks, that is global the range info does not │ │ appear anywhere in the code and therefore you can enter any │ │ value │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3630 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the sort(queue,key) in the zip file will xtrace at runtime │ │ R&D:Ok, I fixed the XTRACE, but the program won't work │ │ anyway until you put the NAME attribute on the Que fields. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3631 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the scrnflds.tpx line 81 should be changed from │ │ %ScreenFieldUse <> %ScreenFieldSetupReturnValue │ │ to │ │ %ScreenFieldUse = %ScreenFieldSetupReturnValue │ │ R&D: Fixed in 3007.100 BrwsGrps.TPX, part of 3007.1 patch. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3632 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/27/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Docs say that Change(?fieldname,value) will update the use │ │ variable with the value and display to the screen. It does │ │ update the use variable but it doesn't display the contents │ │ of the variable on the screen. See test program. │ │ Also in protected mode a change(?fieldname,value) where │ │ ?fieldname is out of range - (field number doesn't exist on │ │ the screen) cause Xtrace. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3633 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Bring up a file to edit. │ │ Mouse click to a new line. │ │ Press ctrl- d to delete. │ │ We are now in mark block to move. │ │ If you arrow to a new line instead this does not seem to │ │ happen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3634 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In Report Writer's formatter from the Data Field window, │ │ pressing F1 brings up the wrong help screen. (Help is about │ │ computed, conditional, total, & runtime fields.) │ │ AppGen's report formatter brings up the correct help screen │ │ from this point. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3635 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3635.zip examples shows a problem when the help screen is │ │ opened. Two grey characters appear on the left side of the │ │ screen. │ │ MD: Seems to be, but may not be, a problem with help screen │ │ formatter so Colvin is looking into it. │ │ MD II: There is definately a problem here, in the meantime, │ │ this person can repaint the _entire_ screen the _screen_ │ │ color (go to options and select the 'Color' button and │ │ paint the screen whatever color is selected here). │ │ MD III: Problem now fixed for 3008! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3636 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : ?? DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There is no verification of a valid helpfile. The help │ │ editor allows you to open and work on any file. Upon saving │ │ the file the file is destroyed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3637 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : ?? DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There is no validation of a help file. The HELP statement │ │ will open any file as a help file. Press 'F1' for help and │ │ the program blows-up! │ │ Bug #3636 already states this. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3638 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I can't seem to type in just a string literal in the │ │ Parameter line of the Contol Field. It wants a use │ │ variable. Generator only. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3639 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Open window one add text. │ │ Open window two add text. │ │ Resize the windows so that you can see both at one time. │ │ Notice how one window border is of a grey shade and the │ │ other is cyan. This is done to show you which one is │ │ currently active. │ │ Press esc. │ │ Choose edit. │ │ You should find that you cannot tell which one is currently │ │ active, and both borders are cyan. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3640 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Skip is not setting the record position correctly. │ │ see uploaded file Todd Seidel cs id 72550,3455 │ │ proj 2992 │ │ file 3640.zip │ │ R&D: There is a bug in his his test program. He is doing │ │ a SKIP(file,1) instead of a SKIP(file,-1) │ │ DH received his new test file see 3640b.zip again. │ │ R&D: SET was not clearing SKIP. This has already been │ │ fixed for 3007.2 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3641 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ @d pictures are returning a -1 │ │ see file 2641.zip │ │ proj 2993 │ │ cs todd seidel 72550,3455 │ │ R&D: Fixed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3642 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Short Description of Bug: @N pictures are broken when using │ │ both INS and IMM │ │ attributes. When you enter a number into the left most │ │ position the ACCEPT │ │ will drop out when you are ESCing past the field. │ │ proj 2994 todd seidel 72550,3455 │ │ test file │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3643 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CT DateReported : 1/28/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : ASCII Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When the FILE structure does not have the CREATE attribute │ │ and a CREATE() is issued, the 'No Create Attribute' error │ │ is not posted for the ASCII driver. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3644 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 2/17/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Example of bug using single component key and locator with │ │ filter. Locator will not locate. See file │ │ cs 76246,246 │ │ rick simi │ │ proj 2995 │ │ R&D: Fixed in 3007.105 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3645 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Bug found in 3007b with a protection fault in protected │ │ mode when you forget to put a USE variable on an Entry in a │ │ repeat structure. │ │ todd seidel 72550,3455 │ │ proj 2996 │ │ bug file │ │ R&D: Fixed for 3008 make. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3646 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ bug report for screen library Problem with SELECT in │ │ non-stop mode │ │ todd seidel cd 72550,3455 │ │ proj 2996 │ │ see bug file │ │ R&D: Fixed for 3008 make. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3647 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Example file for the bug that reboots or xtraces when a │ │ procedure and a routine have the same name. │ │ see file │ │ cis 71033,135 ralph johnston │ │ proj 2999 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3648 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/28/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ msg text is the wrong color and left justified for Radio │ │ buttons. │ │ bug file │ │ cis 75170,110 barry mcclure │ │ proj 2998 │ │ R&D: The supplied program works as advertised for me...no │ │ left justifying and no color problems (3007). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3649 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/29/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This is an uploaded example file. Reboots when he tries to │ │ access help. F1 │ │ proj 2999 │ │ cs id 76627,1532 mark w. coil │ │ R&D: Fixed, next 3008 make. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3651 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The report template create duplicate labels for the │ │ print group footers routine. Example file uploaded. │ │ csid 71534,2666 ken Bame │ │ proj 3001 │ │ see test file │ │ R&D: Fixed in Template Release 3007.102 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3652 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ select does not work as expected on a REPEAT field. See │ │ uploaded file │ │ csid 100267,1023 │ │ gerald me │ │ proj 3002 │ │ R&D: Next 3008 make, fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3653 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the GUI tool will leave black line on the screen when a │ │ form is closed. Uploaded bug file │ │ csid 71740,3221 ben williams │ │ proj 3003 │ │ see bug file 3653 │ │ R&D: The program has two buttons in the update screen which │ │ have no value (BUTTON('')) and keycodes of ESC and ENTER. │ │ This is not proper. Buttons in GUI are NOT exactly text │ │ based sizes, that is why space must be left around the │ │ buttons when designing a screen. What should be done is │ │ design a screen that is bigger than the entry field one row │ │ and one column around the entry like this: │ │ ░░░░░░░░░░░░ │ │ ░@p###-###p░ │ │ ░░░░░░░░░░░░ │ │ ░ = Transparent │ │ Then tweak the row and col parameters so it opens up at the │ │ correct spot. │ │ Next, the program should ALERT both ESC and ENTER and │ │ process them by checking KEYCODE, NOT by putting two "void" │ │ buttons on the screen and assign them keystrokes. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3654 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 1/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Here is some sample code that causes a bug with the GUI │ │ tool. If you use your │ │ arrow keys to scroll up and down on a browse from it will │ │ draw line a cross the │ │ screen. Also it will not calculate the correct row() and │ │ col() values for my │ │ update form. I loaded the new patch for the GUI that │ │ updated it from version 5 │ │ to 7 and it did not fix the problem. │ │ Thank you for the help │ │ Ben Williams │ │ VolCorp 3007 extender and tool chest W4W 3.11, MS-Dos 6.2 │ │ csid 71740,3221 │ │ proj 3004 │ │ see test file 3654.zip │ │ R&D: The crazy "lines" are fixed. However, the other │ │ problem with the ROW() and COL() functions is a user error. │ │ The program is relying on ROW() and COL() of the "Change" │ │ button underneath the list box. Since when you press │ │ "Alt+C", the Change button quickly gets displayed with the │ │ SELECTED color and then back to it's NORMAL color, │ │ therefore ROW() and COL() will return the coordinates of │ │ the button, NOT THE LIST BOX (both GUI and Text modes)! │ │ The correct way to do this would to have a 2 globals (which │ │ this program already has), and when the 1st screen is │ │ opened with the LIST on it, set those globals to the LIST │ │ box's row and column: │ │ GLO:LISTROW = ROW(?ListBox) │ │ GLO:LISTCOL = COL(?ListBox) │ │ Keep in mind that these statements should be RIGHT AFTER │ │ THE ACCEPT since the screen can be moved with the mouse! │ │ Then, in the update proc, the program should do a: │ │ SCREENROW = GLO:LISTROW + CHOICE() - 1 │ │ . │ │ . │ │ . │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3655 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 1/31/94 │ │ Reported In : RevisedDate : 2/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Report Writer │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Edit Menu choice has three D Hot letter choices: │ │ Delete, Draw track, and Duplicate. │ │ It is the same in App Gen's report formatter. │ │ In Text editor, there are two D's (Delete & Draw track) and │ │ two U's (Undo & dUplicate.) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3656 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Example of locator not working properly on a browse using │ │ range limits. │ │ Run the chkbook example. Choose CHECKS from the first │ │ menu. Now choose the third acct (8352-6432-99). When you │ │ get to the browse you will be highlighting the second │ │ record. When you locate check number 2, you will be put on │ │ check number 3. The locator puts you one past the record │ │ you were trying to locate. │ │ R&D: Fixed in 3007.2 template release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3657 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : DBase III Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user claims build() on a dbiii file is acting as if set │ │ deleted is off. docs say it should act as if set deleted is │ │ on. │ │ R&D: BUILD(file) packs the database removing all deleted │ │ records, so the keys cannot contain deleted records. Do you │ │ have an example that shows otherwise? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3658 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : View Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you have an open screen in your application less than 40 │ │ cols and use the view template, when you return, you will │ │ be in 40 col mode. The view template saves the size of the │ │ active screen and restores it. However it is supposed to be │ │ storing the size of the savescreen in the view template but │ │ the save is done before the screen is open. Tom has this │ │ information, just logged for reference │ │ R&D: Fixed in 3007.101 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3659 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : RB DateReported : 1/31/94 │ │ Reported In : 30071 RevisedDate : 1/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CDD created applications are unusable on PC's with CGA. │ │ The flicker effect is similar to scraping one's nails │ │ across a chalkboard. Some sort of environment variable to │ │ enable CGA snow check would do the job: │ │ IE: CLAVIDEO=CGA │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3660 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3 component key with break on the second component only │ │ will break on every record. If I change and create a group │ │ break on the first and second component (even though I │ │ don't want a footer for first component) all is well. I │ │ don't think you should have to break down to the component │ │ you want to use. If so we need to document. │ │ compuserve upload proj 3008 │ │ Frank Menkin 221188 │ │ see file 3660.zip │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3661 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : RB DateReported : 2/01/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Including a file name in the "Other Data" section of FILES │ │ fails to generate the code to open the file(s). │ │ R&D: This is correct operation. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3662 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/01/94 │ │ Reported In : 3006 RevisedDate : 2/15/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Memory Managers │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Harrison A. Curtis 72730,1402 MSG#:52334 │ │ This is the second time in the last two weeks that 3006 has │ │ trashed the program files. The first I could excuse │ │ because I had to abort out of the system while in Clarion3. │ │ However, this evening's case I can't excuse so easily. │ │ I simply left clarion to set up a screen capture │ │ TSR. When I went back in everything was trashed. The only │ │ unique thing I did in the previous session was to press │ │ Scroll Lock and SHIFT Print Screen. The screen printed out │ │ fine and I then left Clarion to load up the │ │ Screen Capture TSR. I did notice that the key map had been │ │ corrupted because the DEL key would no longer delete │ │ (NUMLOCK wasn't on). │ │ I never got the chance to use │ │ the screen capture TSR. As soon as I went back into │ │ Clarion it was trashed. It couldn't find any of the APP's │ │ I was working on, the database drivers were no longer │ │ installed, etc.... I tried CHKDSK and almost all of │ │ the program files that I was working on were broken. The │ │ most important was the .APP. It had been trashed so that I │ │ could load any of the templates for editing. It was │ │ interesting that it had the template │ │ structure/organization. Interrestingly none of the other │ │ files in the directory were broken. This was │ │ definitely the Clarion developer's environment doing! │ │ Even old memories of Microsoft's │ │ first release of the PWB didn't trash the files. It would │ │ blow up now and then, but it didn't corrupt data. Now, │ │ before I do any work I take a backup so I don't loose more │ │ than the session. It may be a good habit, but it is │ │ not speaking well of the developer's environment when it is │ │ absolutely necessary! It is precisely the reason I left │ │ Microsoft for Borland. If it wasn't a requirement by one │ │ of my customers the Clarion package would go on │ │ the shelf. │ │ Yes, you have │ │ provided a better DB developer's environment with the │ │ structured templates. The access to customize the │ │ templates is an excellent idea. It is a significant │ │ improvement over Clarion 2. However, if the enviroment is │ │ so unstable that it drops edits, blasts out your APP │ │ file, destroys a week's worth of development, and breaks │ │ your train of thought - IS IT REALLY BETTER? │ │ I have included the XTRACE.TXT file at the end │ │ of this message. Perhaps it will tell the Clarion technical │ │ staff what went wrong. I don't think so, because by the │ │ time it took the trace the damage had already occurred. │ │ *** Exception 0D : General protection │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3695 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion: allow the user an option to choose whether the │ │ title page should be numbered as page 1. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3665 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/01/94 │ │ Reported In : 3007 RevisedDate : 2/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 MSG#:52750 │ │ Suggestion: Create new Clarion language statement to "fix" │ │ asection of a virtual screen. │ │ Clarion's virtual screen capabilities are one of its most │ │ appealing aspects in terms of enhancing end-user │ │ productivity. It's unfortunate that this area seems to be │ │ getting so little attention. With a little more effort, its │ │ usability could be improved dramatically. │ │ Imagine how useful a split virtual/fixed screen could be. │ │ Itwould put an end to the table/form, list/screen, │ │ select/edit, menu/screen combinations we've made our users │ │ endure for so long. You could have a list box on one side, │ │ and the virtual edit screen on the other and never have to │ │ leave that context. Also, a single set of edit control │ │ buttons (add, edit, delete, cancel, save, help, etc.) │ │ could be used to control multiple list boxes and fields on a │ │ single virtual screen. Right now, only a pulldown can │ │ offer this kind of functionality, because the existing │ │ virtual screen concept is to ego-centric (it effectively │ │ takes over the whole show until closed!) │ │ What do you think? I don't know how that part of │ │ the video library is constructed, but if it wouldn't │ │ require reimplementing the whole thing, this should │ │ really be given some _serious_ consideration. I know in │ │ CDDW what I just described will be extremely easy to do, │ │ even if I have to hand code it (thanks to the all-powerful │ │ "setproperty" statement). I sure hope CDD can play │ │ tag-a-long on this before too long. Danny │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3666 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/01/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul M. Blais 72103,111 MSG#:52380 │ │ The line PRESS(?field,FORMAT(INT_VAR,@D[1-16])) now beeps! │ │ It appears that the separators generate a beep tone for │ │ eachseparator. This was NOT true in prior versions. I work │ │ around it by using the CHANGE() function just fine. │ │ -Paul │ │ R&D:Can not reproduce. I tried PRESS and it worked fine. │ │ Maybe a template problem...?? │ │ R&D: As far as I know, the PRESS command accepts only one │ │ parameter, and yet the example has two parameters. What │ │ EXACTLY is the text that the user is having problems with, │ │ and what EXACTLY is the format of the field processed by │ │ the PRESS? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3667 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tim Murray 73174,3645 MSG#:52415 │ │ My hot record fields don't work any more as of 3007. It │ │ seems the code generates a DISPLAY for the LIST field thru │ │ the LAST field. The fields I want to display are at the │ │ top of the screen before the LIST field. This has worked │ │ fine for 6 months. │ │ From Greg_W: I entered this bug because I think this should │ │ be mentioned in the docs somewhere, (template help,...) │ │ R&D: Repaired in 3007.101 Template Release. │ │ Hot Fields 1) Fields before ?List │ │ 2) Fields between ?List and Locator │ │ 3) Fields after Locator │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3668 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tim Murray 73174,3645 MSG#:52416 │ │ How about adding a feature to Cshell which lets you point │ │ toa file like STUFF.CLA then do a CTRL-C to copy the file │ │ and give it the name *.OLD. Same goes for RENAME. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3669 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Todd Seidel 72550,3455 MSG#:52422 │ │ Would it be possible to get a 3007.2 released quickly to │ │ fix the bug in 3007 with divide by zero giving an error? │ │ Clarion has _allways_ allowed you to divide by zero and │ │ would return zero. Now 3007 gives you a floating point │ │ error and halts the program. I have and I'm sure others │ │ have miles of existing code that we don't want to go │ │ throughlooking for division or modulus operators to work │ │ around this problem. Can we get a quick fix? I've │ │ allready loaded 3007.1 and the problem is not fixed in │ │ this release either. The bug can be repeated with this │ │ code: │ │ ----------------------------------------------------------- │ │ PROGRAM │ │ Val1 LONG │ │ Val2 LONG │ │ CODE │ │ Val1 = 0 │ │ Val2 = 100 / Val1 │ │ !This line causes a floating point error and halts │ │ ----------------------------------------------------------- │ │ If anyone else out there thinks this bug should be fixed │ │ ASAP maybe you could chime in and let Clarion know how │ │ much you would like this fixed. │ │ Todd Seidel │ │ From QA&E: Use CLAMATHTRAP=OFF in your INI file. This │ │ will cause your programs not to trap the "Divide By Zero" │ │ floating point error. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3670 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : VID │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mark W. Coil 76627,1532 MSG#:52470 │ │ I'm using 3007.1 now and just discovered a problem with │ │ debug. If you change a source file, and then run Debug │ │ without doing a make first, Debug crashes the system when │ │ it tries to read the changed source. This occured within │ │ Windows 3.0 and froze windows as well. However, Windows │ │ wasable to recover by terminating Debug with Ctrl-Alt-Del. │ │ Of course, you wouldn't really want to do debug without │ │ doing the Make first, but it can happen inadvertently. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3671 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: jeff palmer 73270,2471 MSG#:52580 │ │ Locators & Ranges in 3007.1: │ │ Has anyone else noticed that if You use range │ │ values and a Locator on the new BROWSE template that it │ │ will always end up one line below where it is supposed │ │ to be! │ │ Here is the setup. │ │ Browse key = Vendor_Key │ │ Component1 = Vendor_Name │ │ Component2 = Part_Number │ │ Browse Setup Screen = Range Limit Field = │ │ POP:Vendor_Name Range Limit │ │ Value = POL:Vendor_Name < Set From │ │ Calling Form │ │ Incremental Locator = Doesn't Matter, │ │ Won't Work │ │ Either Way │ │ Vendor_Name has beed primed in a │ │ prior field from the calling form. From this point hte │ │ BROWSE does in fact only select records that meet the │ │ Vendor_Name. │ │ Now try and use the locator. │ │ It will accept characters and in fact move to a record │ │ but it will be one line below the proper record. I also │ │ noticed upon initial entry to the browse that the HIGHLIGHT │ │ bar is located on the SECOND record on the BROWSE. │ │ If anyone has a fix for │ │ this please let me know. These series of NEW & IMPROVED │ │ "BROWSE" templates are starting to make me crazy! │ │ Signed "Were Making It Easier" │ │ There is 1 Reply. │ │ R&D: Repaired in 3007.2 template release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3672 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Print Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul E. Thomas 70020,655 MSG#:52274 │ │ Please check line 63 in the PRINT.TPX. It currently reads │ │ asfollows: TempPath = TempPath & '\' │ │ I believe it should read as follows: │ │ TempPath = CLIP(TempPath) & '\' │ │ Thanks, │ │ Paul E. Thomas │ │ Eastern Iowa Community College District │ │ R&D: Fixed in 3007.101 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3673 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralph Johnston 71033,135 MSG#:52297 │ │ The Int86X function declaration in the C_LIB.INC file is │ │ still wrong. I know it was reported (I saw it here │ │ somewhere), but I don't find it in the bug file (FIXLST3). │ │ So, for the record, the Int86X function should have the RAW │ │ attribute on it, otherwise it will pass the lengths of the │ │ GROUPs (and the structure, too, I think) which will confuse │ │ the HECK out of the CPU, and most likely send it off into │ │ la-la land. ..Ralph │ │ R&D:Fixed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3674 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: George Hale 72567,2653 MSG#:52247 │ │ Is there ANY possibility of making a file available for │ │ download while we wait for new manuals? The tutorial is │ │ especially a problem. I started trying to make all the │ │ updates in the manuals and realized what a mess I was │ │ making; then I tried cutting and pasting -- even │ │ bigger mess, then I tried just noting which paragraphs │ │ changed, in order to be able to reference back and forth -- │ │ THAT's a pain in the rear, too. I'd surely appreciate a │ │ chance to print out a clean set of documentation and put in │ │ a loose-leaf folder, for now... There is so little bound │ │ documentation that came with the product that re-printing │ │ it ourselves, in this case, wonot be a lot of trouble. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3675 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Todd Seidel 72550,3455 MSG#:52221 │ │ The docs on the ESC attribute say that Clarion normally │ │ backs you out the way you came in unless you use the ESC │ │ attribute. If what R&D told you is correct then the docs │ │ should say that Clarion backs up you up to the prior field │ │ unless you use the ESC attribute. So, the only thing wrong │ │ with the ESC attribute is the documentation not the │ │ functionitself. The LRM statement, "Pressing the ESC or │ │ Backtab key normally selects the previous field in the │ │ sequence that thefields were selected", is wrong. It should │ │ say, "Pressing the ESC or Backtab key normally selects the │ │ previous field." │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3676 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard A Rasbach 71551,3154 MSG#:52255 │ │ The trace helped. The problem is in the Constrained Update │ │ ROUTINE. Just after the PUT statement, it checks for an │ │ error. If an error is found, it sets abortTransaction to │ │ True, issues a ROLLBACK, builds the message and does a │ │ ShowWarnings. The ROLLBACK instruction resets the │ │ ERROR value so the message shows 0. I think the model │ │ needs to be changed so the message is built before the │ │ ROLLBACK is issued. I moved the code in this .CLA file and │ │ then got a Duplicate Record error 40 message. Will │ │ you see that this request gets posted to be fixed for the │ │ next Release? │ │ Thanks for the help. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3677 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: DOUG ANDREWS 73740,2622 MSG#:52182 │ │ When using the error window to find errors in a program, if │ │ you use Ctrl 2 to dup a existing line, the code that keeps │ │ track of program lines and where errors are doesn't get │ │ updated. Enter to add a line or Ctrl C to Copy will keep it │ │ in sync. │ │ Example. │ │ Compile a program with errors on lines 10,11 and │ │ 12. Press Ctrl E and it goes to line 10. │ │ Press Enter and Ctrl E. │ │ It goes to line 12, which was 11 before the │ │ Enter. Still in sync. Now press Ctrl 2 to dup line 12, and │ │ then press Ctrl E. The cursor will move to line 13 when it │ │ should go to 14, which is where line 12 has moved to. │ │ Thanks │ │ Doug Andrews │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3678 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Egbert Dijkstra 100114,56 MSG#:52475 │ │ I used a Btrieve fiel. Just checked and saw that Clarion │ │ file type gives the same result. Did not have a look at │ │ others. I would say a RECORD function on a un-open file │ │ mustnever return a value - so probably a critical error │ │ would be th ebest. Egbert. │ │ From Greg_W: I know this was already reported and │ │ that error checking should be performed. But I just │ │ thought maybe something could be done about this. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3679 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 2/02/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ At runtime, the runtine field entry screen does not allow │ │ enough entry characters to correctly complete the field. │ │ For an @s2 runtime field, only one character can be │ │ entered. For an @s3, only 2, etc. │ │ R&D- this is because internally Runtime fields are stored │ │ as CSTRING and you must allow a null byte at then end of a │ │ CSTRING. Probably should be documented this way! │ │ End User shouldn't have to remember to add a null byte, it │ │ can be added internally. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3680 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul M. Blais 72103,111 MSG#:52609 │ │ 1)I've found some minor GPF's with 3007.1. If you press ^F │ │ inside a screen structure that has EQUATE values in it │ │ BOOM. │ │ 2)I've also noticed a problem if you compile and choose to │ │ see the errors in an external module. If the error was a │ │ missing END or | or any of the numerous end of line / │ │ structure items. You are taken to the right lines and you │ │ can change them all. But when you exit and are │ │ prompted to save the file. The file name / path is blank. │ │ If you choose OK to save BOOM GPF. This happens most if │ │ not all the time this error type is found. -Paul │ │ R&D (Colvin): For #1 above, I need more specific │ │ information or, better, an example of when an equate causes │ │ the xtrace. Equates are not valid in 3.0 for reading into │ │ the screen formatter, but they should not cause an xtrace. │ │ I havn't been able to reproduce an xtrace so far. │ │ #1 above is now fixed - problem was with using an equate │ │ that started with an underbar. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3681 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralph Johnston 71033,135 MSG#:52654 │ │ There is a small bug/annoying feature in the editor (not a │ │ new bug). I'm using 3007. When you have multiple windows │ │ open, and change one window to be in insert mode, then │ │ switch to another window, and then back again, in changes │ │ back to overwrite mode. You can cycle thru all the │ │ windows, putting them all in insert mode, and they will │ │ revert back when you return. Be kind... my insert key is │ │ getting worn out... *grin* │ │ ..Ralph │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3682 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralph Johnston 71033,135 MSG#:52655 │ │ There is a bug in the Editor when you are using Ctrl-M, │ │ Ctrl-C, or Ctrl-D to move, copy or delete a block. After │ │ you have hit Ctrl-M, etc., if you then hit Ctrl-B (a *VERY* │ │ common thing to do for a 2.1-er) the move, copy or delete │ │ is canceled, and a block-mark is started. This is VERY │ │ annoying. When you are in the Ctrl-B block mark, you can't │ │ get back into the Ctrl-M mode. Up to now, the Ctrl-B was │ │ just ignored. My preference would be to have it act like │ │ 2.1 when you are in the Ctrl-whatever mode, since the │ │ Ctrl-whatever starts the block, so a Ctrl-B to mark a block │ │ wouldn't make sense. │ │ There was a suggestion that I thought was │ │ very good a few months ago that suggested to change what │ │ Ctrl-B did, based on one of the options (I think it was the │ │ Zone Insert, but I'm not sure). Maybe a "2.1" keyboard │ │ option, where Ctrl-B toggles Block/Line mode, │ │ instead of Ctrl-L. │ │ From Greg_W: I have duplicated what he is taking about and │ │ it does seem like a problem with CTRL-B. │ │ From QA&E: I don't think it is a problem. These are 2 │ │ completely different editors. with very very few │ │ similarities. I think everyone needs to get with the │ │ program and quit bitching on how it used to be compared to │ │ the way it is now! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3683 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 MSG#:52678 │ │ When using the Search for Text feature of CSHELL it │ │ allowsyou to enter a Search Dir, but if you enter a │ │ directory thatis different from the one you are currently in │ │ it still searches the current directory. │ │ From Greg_W: I duplicated this happening │ │ 3007.1 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3684 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is not documented that if you open a full screen, │ │ keycode() is set to 0. According to R&D, this is the way │ │ it is supposed to work. Can we write it down somewhere. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3685 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ on page 9-9 of the LRM, the bottom of the page gives some │ │ sample color style codes │ │ it says 115 Green on White, it should have number 114 │ │ instead of 115. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3686 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 2/03/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Child Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007 child template with a multi component link causes a │ │ syntax error; it occurs 13 lines below the insert child, │ │ fill secondary within the fill Q routine │ │ DH additional info for other user..... │ │ There seems to be an error in this arena for multi-key │ │ relations... │ │ The result from the code below is: │ │ If Firstfield <> FirstField | │ │ If SecondField <> SecondField | │ │ If ThirdField <> ThirdField | │ │ Execute Code │ │ end │ │ end │ │ End │ │ This gives a Syntax Error..... │ │ Please Check the Template code in the Fillqueues │ │ Routine.... to Correct the │ │ Problem │ │ the >> indicate where I think the problem lies..... │ │ #SET(%IfWritten,%Null) │ │ #FOR(%RelationKeyField) │ │ #IF(%RelationKeyFieldLink) │ │ #IF(%FieldCounter = '1') │ │ #IF(%IfWritten) │ │ OR %RelationKeyFieldLink <> %RelationKeyField #<!If not │ │ in Range │ │ #ELSE │ │ IF %RelationKeyFieldLink <> %RelationKeyField #<!If not │ │ in Range │ │ #ENDIF │ │ #BREAK │ │ #ELSE │ │ #IF(%IfWritten) │ │ >> OR %RelationKeyFieldLink <> %RelationKeyField |#<!If │ │ not in Range │ │ #ELSE │ │ >>> IF %RelationKeyFieldLink <> %RelationKeyField |#<!If │ │ not in Range │ │ #ENDIF │ │ #ENDIF │ │ #ENDIF │ │ #ENDFOR │ │ Andy <<Cowboy>> │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3687 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/03/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Example Applications │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in the example application CHEKBOOK, there is an │ │ 1nreferenced embed in the UpdateCheck procedure, caused by │ │ one of the updates. This embed was an embed for 'OK Button │ │ Press'. This needs to be moved to the 'End of Procedure' │ │ embed because this code actually updates the account │ │ balances. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3688 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/03/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ there is a problem when trying to save changes from the │ │ edit errors window. │ │ - generate app with compile errors in an embedded source │ │ - when compile is complete choose edit errors │ │ - correct the code ( you should be in a window titled with │ │ the embedded source name) │ │ - hit ctrl-x, in the 'Window close screen' it has a prompt │ │ for SAVE FILE. the filename is blank. If you choose 'NO' │ │ or 'CANCEL' you will xtrace. If you choose 'YES' your │ │ changes will be saved correctly. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3689 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 2/03/94 │ │ Reported In : 30071 RevisedDate : 2/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When a Record Filter is false for _all_ records, the report │ │ locks up at runtime if you direct the report to the screen. │ │ (seems to be stuck in a loop) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3690 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/03/94 │ │ Reported In : 30071 RevisedDate : 2/03/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Program: CDD 3007.1 │ │ I am having problems when adding a radio button to a form │ │ screen. To clarify, when you select to add a field, and you │ │ select a field that is │ │ a radio button, the program displays each check box on the │ │ screen for positioning, but when you press CR to accept the │ │ position, the field disappears behind the last field on the │ │ screen. │ │ If you try to add the button again, the program displays a │ │ flashing <! on the screen, and when you attempt to exit, │ │ theprogram locks up! │ │ R&D (Colvin): If anyone can reproduce this, please let me │ │ know how (I sure can't). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3691 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BC DateReported : 2/03/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you link Modula-2 or Pascal code into a Clarion project │ │ and that code uses the TopSpeed Window routines, the linker │ │ says it cannot find ??_wind.lib. This is because this is │ │ supplied with the C compiler and should be part of │ │ ???cla.lib. │ │ The solution is to edit TSPRJ.TXT so that references to │ │ ???_wind.lib for multi-language programming are surounded │ │ by a check for tscla=on. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3692 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/03/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the data pushbutton of a procedure, you cannot enter two │ │ queues containing fields of the same name even though you │ │ have a prefix defined. The generator posts a message, field │ │ name must be unique. There was an earlier bug that when the │ │ code was generated it didn't include the prefix on the │ │ queuebut now it does so there doesn't seem to be a need to │ │ restrict it in the generator. User has requested this │ │ to be changed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3693 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : VID │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the dbugger choose V to view the variables list. If you │ │ hit a letter the prompt will highlight the first variable │ │ starting with that letter. If you hit a letter that no │ │ variable starts with you will lock up. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3694 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Reported by user and verified -- an xtrace occurs when │ │ going in to create a new report and typing in your │ │ dictionary name, vs using the pushbutton, incorrectly. At │ │ the time of hitting the ok button the gpf occurs. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3696 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 2/04/94 │ │ Reported In : 3017 RevisedDate : 2/04/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If a btrieve file is opened in accelerated mode (2h), a │ │ pre-image file is created │ │ Test file - 3696.zip │ │ R&D: The Btrieve TSR creates a preimage file even when │ │ openning in accelerated mode. However, you will note that │ │ this file is always of length 0 (even when you crash the │ │ program), thus indicating that the TSR is not adding │ │ anything to the file. A proof of this is to time adding 50 │ │ records with and without accelerated open. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3697 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : VID │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I'm using 3007.1 now and just discovered a problem with │ │ debug. If you change a │ │ source file, and then run Debug without doing a make first, │ │ Debug crashes the │ │ system when it tries to read the changed source. This │ │ occured within Windows │ │ 3.0 and froze windows as well. However, Windows was able │ │ to recover by │ │ terminating Debug with Ctrl-Alt-Del. │ │ Of course, you wouldn't really want to do debug without │ │ doing the Make first, │ │ but it can happen inadvertently. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3698 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Can we have the message attribute for pulldown items. │ │ R&D: Done in formatters, template symbol still needs to be │ │ added by Vince. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3700 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/07/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Batch Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In 3007 the batch template was changed to open the │ │ primary file before the │ │ Setup Procedure embed point. Since this is inconsistent │ │ with the rest of the │ │ templates, I would think it should be changed back to │ │ having the setup source │ │ point process before anything else happens. │ │ R&D: Fixed in Template Release 3007.101 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3701 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Child Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ You might want to relog as suggestion rather that problem, │ │ but the child template does not support autonumbering. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3702 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 4/01/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Child Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Child template. If you place a calculated field on the │ │ scroll table which is a total which adds up detail │ │ charge ammounts the total is displayed correctly when you │ │ first enter the procedure, however, if you click on any │ │ arrow key, enter the update form the total just keeps │ │ addingand adding and adding. │ │ R&D: As of 3009, the Child template does not have any code │ │ provided to handling the totaling of values in the child │ │ file. If the user has this type of code, it is code that │ │ the user added, and not template code. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3703 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the screen template there is not a close(%pulldown) in │ │ the procedure return │ │ routine. │ │ The following code needs to be added to the routine: │ │ #IF(%PulldownStructure) │ │ close(%Pulldown) │ │ #ENDIF │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3704 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User reports: if two people on a network have the same │ │ record and person one deletes the record, the second │ │ personsget 'changed by another stations' when they try to │ │ save the record, but instead of either ending up back at the │ │ browse, the next record in the key is displayed for the │ │ second person. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3705 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The validate template has too many close(pulldown)'s. The │ │ close pulldown │ │ should be taken out of the LookupValidateCode or out of the │ │ ProcedureReturn │ │ routine. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3706 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/05/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have some browses with _only_ an Exit button (no Insert, │ │ Change or Delete). │ │ When the right mouse button is pressed _outside_ the browse │ │ area it acts as if │ │ the EscKey was pressed or the Exit button was pressed. In │ │ other words it │ │ returns to the calling menu. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3707 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/05/94 │ │ Reported In : 3007 RevisedDate : 3/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests lft rt and center attributes for setmsg │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3708 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/05/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The same bug is in browse, lookup, select and validate. If │ │ you are performing │ │ completion processing on a field that is your Locator, the │ │ 3.007 templates fail │ │ to generate any code for that field. Here's the fix: │ │ #ELSIF(%ScreenFieldUse = %Locator) │ │ #INSERT(%ScreenEditRoutines) <------Add this line │ │ #ELSE │ │ This doesn't seem to be in the new template. I don't know │ │ if he is right, I didn't test it. Thanks │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3709 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/07/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the 30071 templates, the #GROUP %RangeComparison │ │ generates an IF statement, │ │ but does not generate an END. Instead, the END is contained │ │ in Browse.Tpx. This │ │ separation is unnecessary and makes it a pain in the │ │ backside to track down a │ │ missing ENDif, ENDcase, etc. │ │ I think the END statement could easily be moved from │ │ Browse.Tpx to inside the │ │ #GROUP without affecting anything else. │ │ R&D: This is not a bug. In this case, the │ │ %RangeComparison GROUP always generates the same IF │ │ structure. It's what happens if the IF is not met that's │ │ different. Since in some cases EMBEDs need to come between │ │ the IF and the END, it had to be main-line code. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3710 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have just encountered a nasty bug when declaring a │ │ PICTURE type data item. │ │ When I declare an item as record format @N09V2 and display │ │ format @N12.2 and │ │ store a value of 0.00 to it, the actual data stored is │ │ '000000V00' when it │ │ should be '000000000'. If I recall correctly, this 'V' │ │ actually gets inserted │ │ anytime the value is less than 1.00 (i.e. the units digit │ │ masks the 'V'). Not │ │ EVEN acceptable! Can you say 'DATA EXCEPTION'? HELP!!!! │ │ I MUST have this │ │ data format! I'll try doing an INSTRING search & replace │ │ doodah for now, but │ │ that is a real PITA to use all the time! Help me out!! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3711 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53336 S8/3.0 Support │ │ 02-Feb-94 17:46:31 │ │ Sb: 3.007(1) templates │ │ Fm: Advantage Software 100116,3350 │ │ To: sysop │ │ L.S. │ │ This list shows all uses of #IF and #ELSIF (in this │ │ order) │ │ in 3007.1 *.TP? files, where there is a check on a string │ │ constant with letters in it, and where the Template Symbol │ │ is │ │ not UPPERed. │ │ While this might be correct in those cases where the │ │ Template │ │ Symbol is system-assigned only, it is quite certain │ │ incorrect │ │ when the value can be user-assigned (like │ │ %ScreenFieldUse). │ │ e.g., when a user enters the field-equate label of the │ │ cancel │ │ button as ?cancel in stead of ?Cancel (like I myself │ │ happened │ │ to do once), the #IF(%ScreenField = '?Cancel) will │ │ evaluate │ │ FALSE, where #IF(UPPER(%ScreenField) = '?CANCEL) would │ │ evaluate TRUE. As many Template Symbols (like field equate │ │ label) are given a default value, which most users seldom │ │ change, this error might go untrapped for some while... │ │ The [numbers] show the original line number in the │ │ template. │ │ The ------ lines show the name of the template file. │ │ In this list I have not made difference between system (or │ │ template) assigned symbols and user-assigned symbols. │ │ See text file of his list 3711.zip │ │ R&D: This will (soon) no longer be a concern as │ │ evaluations in the template will be case insensitive. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3712 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53339 S8/3.0 Support │ │ 02-Feb-94 17:51:50 │ │ Sb: protected mode change() │ │ Fm: Advantage Software 100116,3350 │ │ To: sysop │ │ L.S. │ │ trying to CHANGE() the contents of a screenfield which │ │ does │ │ not have a CHANGEable contents, like a BUTTON or a LIST, │ │ will │ │ give a XTRACE when running a Protected Mode application. │ │ I think it should post an error() instead. │ │ Arie Rens │ │ Advantage Software B.V. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3713 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 2) In the screenformatter, when one presses [ctrl][right] │ │ on │ │ a space immediatly preceding a word, the cursor jumps │ │ _over_ │ │ the word to the start of the next word. This is │ │ confusing │ │ when one e.g. is busy 'painting' with [ctrl][a] column │ │ headers, and uses [ctrl][right] to jump to the next │ │ word. │ │ 3) In 3007, there appear to be two 'families' of tracks: │ │ mixed and unmixed. The difference appears when one │ │ [ctrl][T]'s a bordertrack in a member of one family, and │ │ then tries to redraw this border by [Ctrl][T]-ing over this │ │ with a member of the other family. When using the [end] or │ │ [home] key, the track will stop 1 character _for_ the │ │ corner, instead of stopping exactly _at_ the corner. │ │ 4) When one chooses for the track the same color as the │ │ screen color, and afterwards changes the screen color, the │ │ track color changes with it. It appears they become linked │ │ somehow, whether one likes it or not. │ │ 7) In the screen formatter, the [grey *] has no effect. │ │ R&D (Colvin): #2 & #7 above are fixed. │ │ (JB): #4 is happening due to any screen data changing color │ │ when the background color is changed. This cannot be fixed │ │ unless ALL screen data is kept in some sort of data queue. │ │ This would be a global change to the screen formatter, not │ │ simply tracking. │ │ #3 Needs some explaination. First, there is a distinction │ │ between "Border" (Ctrl-B) and "Track" (Ctrl-T). They are │ │ completely separate functions. The way that Home and End │ │ work in Tracking is this: if there is a character on the │ │ screen that is in the "track set" (IOW, one of the │ │ characters of the currently-selected tracking scheme), the │ │ cursor will stop at that position first. If Home or End is │ │ pressed again afterwards, the cursor will move to the │ │ respective screen edge. This is not a bug, and has worked │ │ this way since the inception of tracking for CDD. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3714 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/07/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 5) When in the expression generator one does NOT check │ │ 'use │ │ expression generator' the prompts for the formula's and, │ │ in │ │ a conditional formula, the condition stay disabled, │ │ although │ │ one can enter the text field. │ │ 6) Suggestion: place a button for template help in the │ │ formula │ │ editor, so one can more easily get help while filling in │ │ the │ │ formula class. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3715 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 8) In the report formatter, if the cursor is to the left │ │ of at │ │ least 1 data field on the same line, the [grey *] always │ │ acts on the rightmost data field on that line, ignoring │ │ any │ │ other text or datafields between the cursor position and │ │ that │ │ field. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3716 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 3/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In case no one has mentioned it, take note that the on-line │ │ language help omits │ │ any reference to the new statement CHANGE (at least I │ │ couldn't find one). │ │ Danny │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3717 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/07/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you RESET to a deleted record in a Btrieve file that │ │ does not have a memo and you are using NLM 6.1c you will │ │ get a Btrieve error 19. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3718 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/08/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : Implemented │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53513 S8/3.0 Support │ │ 03-Feb-94 14:40:47 │ │ Sb: #53429-3007.101 Template Releas │ │ Fm: Alan L. Schoolcraf 73133,2624 │ │ To: Debby Herman 72662,475 │ │ Debby - │ │ One minor suggestion for a future template update - on │ │ the FORM template, │ │ when deleting, all fields are disabled, including │ │ LOC:MESSAGE. In essence, │ │ this makes the "When delete message" unreadable. (I'm │ │ using GUI). I suggest │ │ leaving the LOC:MESSAGE enabled (or reenabling it) when │ │ deleting a record. │ │ R&D: Implemented in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3719 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/08/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When using the browse as a lookup, on the when field is │ │ selected and using the return field, The code does not │ │ compile. The that generates is field<>field instead of │ │ field=field │ │ R&D: Repaired in 3007.101 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3720 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/08/94 │ │ Reported In : 3007 RevisedDate : 2/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In a memothat has more than a screen full, if you mouse │ │ click on the last line then arrow down some information │ │ gets duplicated as you are looking at it. │ │ For example go to bug number 3710. Mouse click on the │ │ memo. Then mouse click on the last line shown. Arrow down │ │ one line. Then mouse click aggain on the new last line. │ │ Repeat this process to see the problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3721 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/08/94 │ │ Reported In : 3007 RevisedDate : 2/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Debby, I'll try one more time at explaining the dilemma │ │ with alert keys and │ │ locator fields. │ │ 1. As I understand it from examining the browse procedure, │ │ the defined │ │ locator field is processed wholly within the browse.dll │ │ . │ │ 2. One consequence of this is that is impossible to have │ │ embedded source │ │ associated with a locator field. (Even though it appears │ │ that you can │ │ from looking at the field setup screen. If you try to │ │ define embedded │ │ source and then look for it in the browse procedure, you │ │ will not find │ │ it. │ │ 3. What this effectively means is that you can not do an │ │ 'UPDATE(?)' after │ │ completion of a locator field, and even if you could, │ │ the 'BROWSEACTION' │ │ call is at the top of the list box loop. │ │ 4. These problems make Alert keys non-usable for locator │ │ fields in browse │ │ procedures. │ │ 5. It seems that since you cannot define embedded source │ │ for a locator field │ │ anyway, that those options should be disabled when you │ │ enter the field │ │ setup screen from a locator field. │ │ 6. The only way I can see that Alert keys could be used on │ │ locator fields, │ │ is to selectively allow the Alert key to do an │ │ 'UPDATE(?)' if the Alert │ │ key is defined for a locator field. │ │ 7. If I'm missing something here, please let me know, and I │ │ would also like │ │ to know what the likely action that you will take to │ │ resolve any or all │ │ of the described issues. │ │ Thanks, Jim Grotjan │ │ UID: 207934 │ │ Ph#: 817-284-3208 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3722 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/08/94 │ │ Reported In : 3007 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ actually the select template -=- select template problem │ │ where pressing anything completes the select when having │ │ just a select and exit button. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3723 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/08/94 │ │ Reported In : 3007 RevisedDate : 2/08/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : DBase III Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The dBase driver cannot read an index which has an │ │ expression of the form str(field). │ │ R&D: The cause of this is that the expression handler was │ │ case sensitive. The work around is to do STR(field). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3724 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/08/94 │ │ Reported In : 3007 RevisedDate : 2/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jared Davis 72571,2123 MSG#:52180 │ │ Subj: 3007 File Struct import │ │ I can not get the "File", "Import", "File Structure" │ │ command to properly import a file definition when the file │ │ label has exactly 17 characters. │ │ Under 3006 the file label imported is missing the 13, 14, │ │ 15and 16th characters. Under 3007 the file label is correct, │ │ but there is no space between the file label and the FILE │ │ keyword. │ │ From Greg_W: I created and example that demonstrates the │ │ problem. (3724.zip) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3725 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 2/08/94 │ │ Reported In : 30071 RevisedDate : 2/08/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Change POOLLMT.DOC in reqards to ROUTINEs and how they are │ │ NOW (as of 3007) treated by the compiler. Since ROUTINE's │ │ which were the main cause of POOL limit problems are now a │ │ thing of the past. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3726 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 2/08/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Child Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Child tempalte does not support autoincrementing a unique │ │ autoincrementing key in the child file. (I'm assuming that │ │ the keys are defined properly in the dictionary) │ │ parentfile - OrderNumKey │ │ - OrderNumber │ │ childfile - OrderNumkey (Unique,Autoincrementing key) │ │ - OrderNumber │ │ - LineItem │ │ This should be documented as Not Support in this Template │ │ or added to a future release. │ │ R&D: This is documented (in the template) as not supported. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3727 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/08/94 │ │ Reported In : 30071 RevisedDate : 2/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Compile Eatmem.Cla and Runerr.Cla in protected mode and │ │ protected dll. Using a LONG data type 47/10 = 40, after │ │ the run it = 50. This only happens after a RUN and │ │ compiled in the two models above only!!! Note in │ │ RUNERR.CLA I am doing a RUN to c:\nu\si.exe (Norton). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3728 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/08/94 │ │ Reported In : 30071 RevisedDate : 2/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the GUI DOC'S it states, do not place anything in the │ │ first two colums on the screen because of the border. If │ │ the border is off, why does this rule still apply. At │ │ runtime the screen is real funky. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3729 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ if you try to place radio buttons on a form by only using │ │ the mouse, clicking with the mouse to place them where you │ │ want them doesn't place them there, they disapear off the │ │ form. │ │ R&D: Correct - the move paradigm, implemented in 3007, │ │ requires that the mouse button must be pressed and held │ │ WITHIN the marked area. Clicking outside of the marked │ │ area says to unmark the area (thereby losing the field in │ │ this particular case, since it didn't exist before) and │ │ begin marking a new area. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3730 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When defining a string(@n_p.d), is it valid to leave the │ │ decimal places off if they are zero? │ │ String(@n_9) CREATE() returns invalid field type │ │ descriptor as compared to string(@n_9.0) which works fine. │ │ In the generator since there is no error check after the │ │ create() statement you get a file not found error returned │ │ by the open(). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3731 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when adding a module to the application it allows you to │ │ type in lower case but the module is added in uppercase. │ │ if the case of the module name is modified to lower case │ │ the change does not get saved. │ │ R&D: The lower case entry behavior is for the purpose of │ │ entering project system prefixes ONLY (ie. %clapfx%...). │ │ Since DOS is case-insensitive to "real" file names, │ │ (xyz.doc = XYZ.DOC) we just chose a convention of always │ │ UPPERcasing "real" file names for clarity on the Module │ │ View. NDOS uses the opposite lowercase convention when │ │ displaying a DIRectory of filenames on disk. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3732 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In both report formatters go to the report options. Choose │ │ the down arrow selection for page number. Choose the │ │ number radio button and then tab to change the page length, │ │ make the change and then hit ENTER. When you are returned │ │ back to the previous screen, you should see page length is │ │ blank. If you click or tab to the OK button it get saved │ │ fine. Since the length does not get saved the next time │ │ you go to change the length the variable radio button is │ │ marked. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3733 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JD DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In RW formatter, if you create a total field to count the │ │ occurances of a string field and select non-zero or zero, │ │ ittreats all strings as equal to zero. Thus if the count │ │ field is set to count zeros, it counts all records. If set │ │ to count non-zeros, it count no records It should treat a │ │ null as zero & any value as non-zero. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3734 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ browse -- with a range limit and a locator. Type in a │ │ higher value than the last record. This will cause the last │ │ record to be removed from the list box -- │ │ R&D: Fixed in 3007.2 template releases │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3736 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The environment variable ClaRunFlush=ON is only freeing up │ │ 16 bytes of memory according to the RUNIT.CLA program. │ │ After each run, type mem /c and type EXIT to execute the │ │ next run. There is a total of four runs. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3737 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Attached file shows bug with word wrapping in a text field. │ │ Text field is doing some type of word wrapping when │ │ selected but doesn't actually word wrap until completed. │ │ When is is supposed to word wrap and if it is not supposed │ │ to word wrap until completed shouldn't their be no change │ │ in the text until that time. │ │ see file 3737.zip │ │ reported by scott merritt │ │ cis id 71140,2502 │ │ proj 3050 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3738 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ lookup problem with a BROWSE. │ │ Problem: │ │ I want the users to move through the fields via the TAB │ │ key. If the users decides to make an entry then TAB this │ │ entry is tested against a lookup file in the embedded │ │ source. If the entry is not found a BROWSE is executed as a │ │ LOOKUP "setkeycode(ShftEnter)". The user has a choice │ │ to DOUBLE CLICK on the record or CLICK on the SELECT │ │ button, if the user CLICKS on the SELECT button the │ │ RETURN FIELD is not filled. If the user DOUBLE CLICKS │ │ everything works correctly. │ │ see file 3738.zip │ │ R&D: Fixed in 3007.2 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3739 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you open a file in accelerated mode and someone else has │ │ the file open in a different mode, the program stops with │ │ Btrieve error 88. │ │ R&D: This now returns Clarion error code 5 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3740 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a listbox that does not have a horizontal scroll bar will │ │ scroll one position to the left/right at runtime │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3741 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : BASIC Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Supplied file shows a problem in the BASIC drivers │ │ buffering code. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3742 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This zip contains an example using 3007.101 of a bug in the │ │ help system. You'll find screen corruption. │ │ uploaded cs file │ │ 3742.zip │ │ cs id 72170,1767 regis w kern │ │ proj 3054 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3743 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mike Hanson, BoxSoft 73234,1447 MSG#:53565 │ │ Hi! Just a wish that I've mentioned a couple of times, and │ │ it shouldn't be too tough to implement. With the advent of │ │ 3.0, the interface designers at Clarion decided that some │ │ people working with the Editor would like to mark blocks │ │ for operations before actually deciding which operation to │ │ perform (ie: the "Mark Block First" option). This is not a │ │ problem, as it is an option. The problem is that the Ctrl-B │ │ key was stolen for this pursuit, and Ctrl-B's functionality │ │ was moved to Ctrl-L. │ │ I am requesting that you treat Ctrl-B as Ctrl-L if the │ │ "Mark Block First" option is disabled. The main reason I │ │ want this is that I normally let my fingers hover over │ │ Ctrl-C and Ctrl-B, while maneuvering with the cursor keys. │ │ By forcing me to use Ctrl-L, I must repeatedly │ │ return my hand to the home row because I continue to forgot │ │ to hit Ctrl-L before heading off to the cursor keypad. │ │ This would make me very happy. I thought I │ │ had gotten over it, but after using CDD3 for over a year │ │ I've decided that there is a better way. Please put some │ │ consideration into this. It shouldn't be too tough to do. │ │ Thanks in advance! Catch you later! │ │ -=> Mike Hanson, BoxSoft <=- │ │ There is 1 Reply. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3744 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 MSG#:53581 │ │ In the 3007.101 FORM.TPX there is a line that needs to be │ │ changed. This will allow the user to hit ESC on the │ │ pulldown (if any) that is on the form. This ESC will │ │ return the user to the form instead of exiting the form. │ │ The line that needs to be changed is line 355. It needs │ │ to be changed from: │ │ IF FIELD() <> ?Cancel │ │ To: │ │ IF FIELD() <> ?Cancel and FIELD() > 0 │ │ Regards, │ │ Fred Schmitthammer │ │ Professional Practice Systems, INC. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3745 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ App demonstrating computer crash when opening several local │ │ btrieve files. │ │ file 3745.zip │ │ cs id 70436,207 stan hargrove │ │ proj3055 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3746 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Place an image button on the screen, check Display from │ │ field. Exit out of screener and come back to the same │ │ button. Now the Display from file button is checked. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3747 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : DOS Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CREATE() for a DOS file does not return an error if there │ │ is no create attribute │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3748 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Child Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Child template will generate with compile errors if fixed │ │ rows in the list box. │ │ See application in 3748.zip │ │ csid 71302,2102 │ │ john milhoan │ │ proj 3056 │ │ Fixed with 3007.2 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3749 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Wayne Freeman 76314,2100 MSG#:53588 │ │ An Incremental Locator field on a browse/validate in GUI │ │ loses its bottom border. The same field generated without │ │ the Incremental Locator property is okay. │ │ BTW, I reported this after 3006 was released, too. I │ │ don't remember the bug number, though, sorry. │ │ Wayne │ │ From Greg_W: The previous report was Bug# 2704 and is │ │ flagged NotABug. I just duplicated the problem in 3007.1 │ │ and it definitely has something to do with the SHOW │ │ statement that the incremental locator code generates in │ │ the Browse Template. │ │ Example File: 3749.ZIP │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3750 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The use of Ctrl-Home does some really wierd things. For │ │ instance it will remove the text of you buttons if they │ │ happen to be to the left of the cursor when Ctrl-Home is │ │ pressed. It will remove sections of ListBoxes, Radio │ │ buttons all kinds of things. │ │ These will all be returned to the screen if you press │ │ Ctrl-End. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3751 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 2/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Short Description of Bug: The CAPs attribute will not work │ │ in protected mode │ │ on ENTRY fields within a REPEAT structure. An Xtrace will │ │ occur. │ │ see file 3751.zip │ │ csid 72550,3455 todd seidel │ │ proj 3057 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3752 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Short Description of Bug: When you try to create a betrieve │ │ file that is │ │ defined within a procedure and there are 3 or more │ │ components in a key │ │ an xtrace will occur when you open a screen after the │ │ create operation. │ │ It appears the memory gets corrupted by the create. │ │ file 3752.zip │ │ csid 72550,3455 todd seidel │ │ proj 3058 │ │ R&D: This is the same as bug#3745 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3753 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/10/94 │ │ Reported In : 3007 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007.1 - on a FORM when you try to place radio buttons on │ │ the screen and the text of one the options ends on column │ │ 80of a 25 x 80 screen, you can't select any of the buttons │ │ when compile and run the application, if it's moved off of │ │ column 80, it works fine. │ │ refer to 3753.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3754 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : CPD 21 Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Form21 template is missing referential integrity code. │ │ Example: When compiling the COOKBOOK.APP found in 2.1 │ │ examples, RI:RestrictDelete and RI:RestrictUpdate are not │ │ declared, causing compile errors. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3755 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 2/10/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ClaCnv │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ MAKECOLOR is converted with three parameters instead of two │ │ that is listed in Language reference manual.... │ │ R&D: Fixed - the third param was an existing border color │ │ in the SETHUE statement, which is now being deleted. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3756 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/10/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007.1 - if the app is in MODULE view, you can't hi-lite a │ │ module and press CTRL+F8 and have that module appear in the │ │ editor like you could in 3006. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3757 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/10/94 │ │ Reported In : 3007 RevisedDate : 2/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53185 S8/3.0 Support │ │ 02-Feb-94 08:28:38 │ │ Sb: _Clipper DRIVER????????? │ │ Fm: Rob Mousley 100075,772 │ │ To: Debby Herman 72662,475 │ │ Hi Debby │ │ The new "Clipper driver" seems to have a few minor │ │ problems... │ │ Enter a file layout into the dictionary. Mine looks like │ │ this: │ │ CLIPTEST FILE,PRE(CLI),DRIVER('CLIPPER,CREATE,RECLAIM| │ │ NAME('CLIPTEST.DBF') │ │ BYNAME KEY(+CLI:NAME),DUP,NOCASE,NAME('BYNAME') │ │ RECORD RECORD │ │ NAME STRING(20),NAME('NAME') │ │ .. │ │ (This is not exactly complex - all defaults accepted for │ │ NAME attributes etc.) │ │ Hit File, New, Database, specify CLIPTEST.DBF, the │ │ dictionary. │ │ The file comes up empty - so far so good. Press Ins, enter │ │ info into the │ │ field. Click on Ok... BAM! Hung, no XTRACE/Error msg, │ │ nothing, just hung. │ │ Fortunately CtrlAltDel still works. │ │ Ok, create an app, specify the file, put in a single │ │ Browse/Form combo. Make & │ │ Run. Error msg: Code 47, Invalid Record Declaration. │ │ (You see, the database │ │ manager had created a .DBF something...). Delete that DBF │ │ & NTX. Re-run the │ │ app. This time all works ok. So far so good. Go back │ │ into the database │ │ manager - this time it shows the message 'File not open' │ │ <???!!!&%$#>. │ │ (Incidently I had a few nasty unexplained crashes which │ │ involved my QEMM memory │ │ manager along the way - unrepeatable.) │ │ Scott, this happened for me also. Attached file has the │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3758 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : VID │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ copy of previous history bug...... │ │ You cannot debug local data in a routine. In other words, │ │ if I create a local variable and I use it throught the │ │ procedure and in a routine in that procedure, I can no │ │ longer see that value using trace, examine or display of │ │ local variables. │ │ QA: Since ROUTINEs are now look like "Procedures" they do │ │ not have local data! All local variable to the procedure │ │ are concidered Local Variables of a Parent procedure when │ │ you are in a ROUTINE debugging it. You still have access │ │ to them however it is not via the ALT-F5 hot key. I doubt │ │ this will evr change. │ │ Did he mean "however it is via the ALT-F5 hot key" ? │ │ If so this seems to be only available in protected mode?? │ │ This is a message from Compuserve user. │ │ 1. If I compile in protected mode then the debugger is │ │ working for the most │ │ part correctly. At least I see the local variables to │ │ proceed with debugging. │ │ If I hit Alt-F5, I get a complete list of the local │ │ varables while in a │ │ ROUTINE. If I use F5 to simply trace the variables being │ │ set while stepping │ │ thru the code, I get at least all the numeric variable │ │ traced (including local │ │ variables). I still do not see the results of any instance │ │ variables. │ │ 2. If I compile using overlays instead of Protected Mode, I │ │ can not access any │ │ local varables once in a ROUTINE. This includes pressing │ │ Alt-F5 and then │ │ ENTER. According to the debugger there isn't any local │ │ variables to trace. │ │ The only difference between ! and 2 is the setting of the │ │ PROTECTED or Overlay │ │ check box in the Project Settings screen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3760 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : RB DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/25/94 │ │ Fixed In : Status : Response │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Search doesn't always work in a source embed in a source │ │ only procedure. Searching for the string ! broken will │ │ fail even though the string is definitly there. This is │ │ not reproducable in a small APP. This only seems to occur │ │ in an APP with several procedures (all of them Source). │ │ Searching for the ! broken string seems to work OK all the │ │ time in the editor itself. │ │ R & D - We discovered that the App's embedded source had │ │ gotten corrupted and thus things did not perform correctly. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3761 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : RB DateReported : 2/10/94 │ │ Reported In : RevisedDate : 2/10/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about adding a new validation type to the │ │ dictionary and Screener similar to "Must be in List" except │ │ instead of Buttons, we have a drop down list box with a │ │ Arrow () at the end of the field. This would make the DOS │ │ product behave even more like the Windows product. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3762 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the help screen for the debug settings is missing help for │ │ the project include radio button │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3763 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ We define a global variable GLO:Paglen which we set prior │ │ to running a report. │ │ We define our report page length equa to GLO:Paglen. The │ │ problem is when we │ │ get back into the report formater (editor) in the APP. The │ │ first time we get │ │ into a report formatter in a NEW CDD Session, the report │ │ page length goes back │ │ to 60 and we have to reset it to glo:paglen. This only │ │ happens the first time │ │ in a new CDD session and it only happens when we get in to │ │ the report formatter │ │ -- other editing on the procedure doesn't affect it. │ │ DH I was able to reproduce this bug. If you can't let me │ │ know. Thanks │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3764 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/10/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ My problem was in a SCREEN template in which I defined NO │ │ files in the TOP portion of the FILES screen. In 3006 the │ │ template would open NO files for me │ │ -- which is the way I want it. I did define some files in │ │ the BOTTOM poetion of the screen so I could reference their │ │ variables in the screen formatter. What happend is that the │ │ generated code automatically opened the first one of │ │ the files in the BOTTOM part of the screen as if it were │ │ the file in the TOP. This gave me an error because the │ │ variable file name was null and the file could not be │ │ openedsuccessfully. Of course, I was able to work around │ │ it, but I thought you would like to know about the strange │ │ behavior. │ │ DH I get the same results. Has this process │ │ changed? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3765 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you declare a screen in the MODULE static │ │ area, and then open it in a procedure, it will NOT be │ │ closed. │ │ If the screen is declared locally it is closed. │ │ I looked to see where the auto-close feature is documented. │ │ It isn't. It should be. Maybe you could make that a │ │ suggestion to Documentation. │ │ CS message - good point. I don't see anything in the docs │ │ that describe screen closing. In addition maybe it could │ │ explain that you can Close a full screen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3766 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/10/94 │ │ Reported In : 3007 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ No where is it documented that SELECTED() will take in │ │ concideration Skipped fields, or what value it takes upon │ │ opening the screen. There is also no mention as to the │ │ EFFECT of DISABLE()ing fields and the effeft as to what │ │ SELECTED() should be after the screen is opened but before │ │ the ACCEPT. │ │ It's a pretty cloudy area that needs some more light. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3767 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The clipper driver using only one numeric field which is │ │ the only field in the file will not allow the file to be │ │ created. See test program 3767.zip. │ │ R&D: The test program had an invalid field description │ │ Q&A: You are correct! Index with one Real(numeric passed) │ │ String with an @n_9.2 passed. We do not have a bug. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3768 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ SELECTED() does not seem to return an accurate field number │ │ if I have disabled some fields after opening the screen and │ │ prior to hitting the Accept statement. │ │ See test file. │ │ R&D: As we discussed...not a bug. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3769 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ if i presss CtrlInsert during an ASK, then KEYCODE() │ │ returns3123, not 3122...this error is prevelant in all │ │ keycodes i stated, 3117-3136. cdd makes no use of the 3117 │ │ keycode and will never be returned, as far as i can tell. │ │ see example program 3769.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3770 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ if you import a 2.1 .APP file into 3.0 and a file in the │ │ 2.1 app does not have keys, then the nokey files will not │ │ get generated correctly. I deleted the file from the DCT │ │ and imported the definitions from the files themselves and │ │ everything works. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3771 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the 3007.101 FORM.TPX there is a line that needs to be │ │ changed. This will allow the user to hit ESC on the │ │ pulldown (if any) that is on the form. This ESC will │ │ return the user to the form instead of exiting the form. │ │ The line that needs to be changed is line 355. It needs │ │ to be changed from: │ │ IF FIELD() <> ?Cancel │ │ To: │ │ IF FIELD() <> ?Cancel and FIELD() > 0 │ │ Regards, │ │ Fred │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3772 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/10/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Regarding editor hot keys....why not provide, in a setup │ │ type environment, the capability to assign user (us the │ │ programmers) defined control keys for all the │ │ functions. Then if you liked Ctrl-B better than Ctrl-L │ │ then you could assign │ │ it in your environment setup. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3773 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I'm in CShell. I tag most of the files in a large │ │ directory and │ │ I'm sitting at the bottom of the list. I │ │ delete all tagged files. │ │ The list is blanked. If I press Ctrl-PgUp I │ │ can recover from │ │ this. If, however, I attempt to scroll up with │ │ the Up-Key, the │ │ system will XTRACE. │ │ R&D: This has been fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3774 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : RevisedDate : 2/15/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mike Hanson, BoxSoft 73234,1447 │ │ To: Greg Whitaker 76711,1035 (X) │ │ I often change APPs using CShell while still in an existing │ │ APP. That is, I am in one APP (not saved), and I press F10 │ │ to get CShell. I choose another APP and press Enter to │ │ loadit. │ │ 3006 would have saved the current APP, then loaded the │ │ otherone. 3007 gives me the error message "AppName1.$$$" │ │ exists.Catch you later! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3775 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The help screen for the List template procedure is missing │ │ info about the 'Start of Fill' embed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3776 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53793 S8/3.0 Support │ │ 05-Feb-94 09:42:03 │ │ Sb: BFLOAT BUG │ │ Fm: Tim Mirande 76011,3112 │ │ To: Tech Support │ │ Hi Debby, │ │ Here's a bug in 3007.1 that is very easy to replicate. │ │ For both versions of BFLOAT fields (4 and 8), if you │ │ multiply by negative 1 (to reverse the sign) and the │ │ number │ │ happens to be zero, the result value is calculated as high │ │ values. In other words, │ │ Loc:AnyFloat = 0 │ │ Loc:AnyFloat *= -1 │ │ Loc:AnyFloat will be high values. │ │ New math? <g> │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3777 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53798 S8/3.0 Support │ │ 05-Feb-94 10:38:56 │ │ Sb: Screen Bug │ │ Fm: Tim Mirande 76011,3112 │ │ To: Tech Support │ │ Hi Debby, │ │ About a month ago, I left a bug report and an example app │ │ relating to the (3006) screen library. It demonstrated a │ │ bug │ │ that when using the IMMediate attribute on input fields, │ │ cursor movement would act erratically using any of the │ │ three │ │ methods of field movement; tab key, alt/key, mouse. │ │ To refresh your memory on the subject, you left me this │ │ message in response to my bug report: │ │ >>> Thanks for the upload of the file bugrpt.zip. I │ │ have │ │ reported this as bug number 3422. The problem has to │ │ do │ │ with the immediate attributes on your fields. If you │ │ remove them, all is okay. The problem is easily │ │ duplicated with your program so R&D should be able │ │ to │ │ get it fixed for the next release... │ │ Well anyway, in 3007.1, the problem is fixed relating to │ │ cursor movement with the tab key and the alt/keys. │ │ However, │ │ the problem still exists when selecting fields with the │ │ mouse. If you have about 15 fields on the screen and your │ │ cursor is on the first or second field and you click on a │ │ field near the end, the cursor jumps to the NEXT field │ │ (not │ │ the field you're clicking on) for 3 clicks. It then jumps │ │ to │ │ the appropriate field. Again, this problem only manifests │ │ itself when you have the IMMediate attribute on and when │ │ selecting fields with a mouse. │ │ Let me know if you would like me to re-upload my example │ │ app. │ │ It is, however, very easy to replicate. │ │ Thanks for your assistance! │ │ R&D: I put several fields on the screen with IMM │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3778 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53807 S8/3.0 Support │ │ 05-Feb-94 11:45:36 │ │ Sb: #ADVANCED.APP PROBLEM │ │ Fm: Randy Rogers 75730,1337 │ │ To: Debby Herman 72662,475 │ │ Tom, │ │ Tried your ADVANCED.APP and ran into the following problem: │ │ Select Address record 1 for modification in the Personal │ │ Address State field │ │ enter CD left click mouse on OK button select state table │ │ appears point mouse │ │ to DC then left click once highlight bar moves to DC - │ │ District of Columbia │ │ point mouse to select button then left click once │ │ the following error box appears: │ │ Error 35 Record Not Found The value you enter must exist in │ │ the Parent File ( 1 │ │ side of 1:Many) file │ │ Regards, Randy Rogers Keystone Computer Resources │ │ R&D: Fixed (Actually a template bug) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3779 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53808 S8/3.0 Support │ │ 05-Feb-94 11:45:39 │ │ Sb: CDD XTRACES │ │ Fm: Randy Rogers 75730,1337 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ When working in OS/2 if you are debugging a program in a │ │ separate dos session │ │ and discover a problem (and forget to exit VID) when you │ │ switch back to │ │ clarion, correct the error and then try to re Make the │ │ program, Clarion will │ │ XTRACE. This is likely because VID (in other session) has │ │ the exe locked/held. │ │ Clarion should detect that the exe is locked/held and │ │ report some error - not │ │ XTRACE and lose all my modifications!!!!! │ │ Regards, Randy Rogers Keystone Computer Resources │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3780 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Are the 'B' (sound on/off) and 'V' (screen blanker) │ │ switchesfrom earlier Clarion releases no longer supported in │ │ CDD 3? The sound on/off is impt to a number of our users - │ │ how can I get the equivalent of B=NO in CDD 3? -dave cohen │ │ Can we add the b=no ability. Through API? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3781 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 │ │ To: Debby Herman 72662,475 │ │ Debby or Tom, │ │ The List box template help still says that it has a │ │ "Process Selected │ │ Record" embed, but in reality it does not. Could it make │ │ it in the next │ │ template release? │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3782 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/11/94 │ │ Reported In : 3007 RevisedDate : 2/11/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports-=- total fields with a label of just one │ │ character basically get lost. In other words you cannot │ │ press ctrlf and change them nor do they end up in the │ │ report structure as code gets generated │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3783 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ File showing the browse that will not redisplay the list │ │ upon return from the update form. 3007.102 templates │ │ see file 3783.zip │ │ ts proj 3068 │ │ R&D: Fixed with 307.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3784 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Clipper driver does not allow indexes to be built on │ │ dates. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3785 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ i have a browse with no locator. when i tab between the │ │ fields, the │ │ browseaction does not trigger the ProcessField event. if i │ │ add a locator it │ │ does. it seems in the ACCEPT loop of the browse.cla, it │ │ does something to the │ │ effect: │ │ ACCEPT │ │ CASE FIELD() │ │ OF Locator │ │ ... │ │ etc. │ │ but if form has no locator, then Locator is 0 and FIELD() │ │ always returns 0 when │ │ not in the List. therefore, it always executes the OF │ │ Locator code and not │ │ code for processing next field. i added a new OF section │ │ before the OF Locator │ │ to the effect: │ │ ACCEPT │ │ CASE FIELD() │ │ OF 0 │ │ do stuff you would do if field had │ │ change... │ │ OF Locator │ │ etc... │ │ and this seems to correct the problem, if this is even a │ │ problem. it may not │ │ have been designed to really handle this, but i require it. │ │ as when you tab to │ │ a button for whatever reason, then Field Setup Procedure │ │ should always be │ │ triggered for buttons. │ │ R&D: I believe this is fixed in one of the 3007.10x │ │ template releases. What version of the templates is the │ │ user working with? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3786 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Doing a SET(key,key,0);NEXT(file) on NLM 6.1e returns an │ │ empty record and the following NEXT gives a Btrieve error │ │ 19. │ │ Workaround: Do SET(key,key) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3787 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 54207 S8/3.0 Support │ │ 08-Feb-94 03:04:18 │ │ Sb: _report_break │ │ Fm: Rob Mousley 100075,772 │ │ To: Debby Herman 72662,475 │ │ Hi Debby, │ │ there seems to still be a problem with group breaks in the │ │ report template (3007.1). │ │ The key has three components, breaks are on the first two. │ │ The problem occurs │ │ when you have a record filter in the report. The template │ │ generates code │ │ similar to : next(file) │ │ save footer routine │ │ filter expression │ │ If you change this to │ │ next(file) │ │ filter expression │ │ save footer routine │ │ the problem disappears. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3788 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 54418 S8/3.0 Support │ │ 09-Feb-94 03:57:28 │ │ Sb: #54322-Locator field alert keys │ │ Fm: Juergen Bartsch 100020,1044 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ if Tom is already working on the locatorthing it would be │ │ nice if he could look │ │ at the problem that I can't type german characters (o,u, a │ │ with dots) at the │ │ first position of the locator field. Workaround: type first │ │ a "legal" │ │ character, press backspace - then you can type any special │ │ character you want. │ │ rgds Juergen Bartsch │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3789 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 3007` RevisedDate : 2/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The following test leaves a HELD record in a file due to an │ │ error in │ │ 3007.101 Form.Tpx. │ │ 1) Create a file (Names) having 2 fields - Nam:NameID │ │ (AutoInc), Nam:Name │ │ 2) Add two keys - one on each field and make them UNIQUE │ │ 3) Create a second file related to Names using Nam:NameID │ │ as the Link │ │ 4) Define relation as restricted │ │ 5) Using typical Browse and Form, add names Debby, and │ │ Debbie │ │ 6) Now select one name (Debbie) and change it so that it │ │ will cause a │ │ Duplicate Key Error (Debby). │ │ 7) Result - error shown is a transaction error (incorrect) │ │ noting that │ │ original values will be restored. Values are │ │ restored, but further │ │ changes are not possible because the HOLD has not │ │ been released. │ │ Douglas │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3790 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Pulldown Menu Editor Window reads, "Press Ins to Insert │ │ an item below.." │ │ (two periods, should be only one). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3791 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Pressing ALT+O on "Button Field Properties" window after │ │ editing source │ │ button (which are missing hot keys BTW) puts cursor on line │ │ 1, causing │ │ automatic virtual scrolling to occur. Great way to lose │ │ your place <g>. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3792 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3. Scroll lock on a virtual screen while "Field Selection" │ │ dialog window is │ │ displayed causes the CDD dialog window to scroll rather │ │ than the field pointer │ │ R&D (Colvin): This is defined behavior for ANY virtual │ │ screen when scroll lock is turned on. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3793 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 4. On the "Select String Field Colors" dialog window, if │ │ both "No Color │ │ Selection" and "Foreground Color Only" are checked when the │ │ window opens, │ │ deselecting "No Color..." and then "Foreground Color..." IN │ │ THAT ORDER will │ │ display TWO, not one normal attribute options. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3794 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 5. Alerting and then pressing the same key that appears as │ │ a hot key on a │ │ pulldown menu option causes the program to freak out and │ │ eventually hang or │ │ reboot the computer. │ │ R&D: Can't dupe...need example. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3795 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 6. CHANGE statement - if value in second param (variable) │ │ exceeds length of │ │ target field, the remainder of the value will be stuffed │ │ into the next field │ │ that is selected. Passing the substring of the value using │ │ cols(?), etc., does │ │ not work. Can find no other workaround. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3796 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 7. API RepositionScreen(row(?),1,rows(),cols()) will cause │ │ a EXTENDLL program │ │ to reboot the machine after displaying a protection │ │ violation warning for 1 │ │ second if the region extends beyond the actual number of │ │ rows remaining in the │ │ current screen structure. Very nasty. Programs compiled │ │ under DYNALINK do not │ │ manifest this anomoly. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3797 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Operating System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Opening a virtual screen in two DOS boxes at the same │ │ time (one EXE the │ │ other in Generator's screen formatter) causes "Violated │ │ System Integrity" │ │ error". │ │ 2. Pressing ctrl+break to terminate a Clarion EXE compiled │ │ using DYNALINK model │ │ while CDD is loaded in another dos BOX almost always causes │ │ "Violated System │ │ Integrity" error". The problem is even worse using EXTENDLL │ │ model. (Actually, │ │ I've been experiencing many strange problems during program │ │ termination in │ │ general). │ │ 3. (related to #2) - Shutting down CDD while DYNALINK EXE │ │ is running in another │ │ DOS box almost always causes "Violated System Integrity" │ │ error". │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3798 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/12/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Hide mouse pointer when keyboard is accessed, revealing │ │ it again only when │ │ mouse movement is detected. This keeps it out of the way │ │ when it obviously │ │ isn't needed--very programmer friendly (hint). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3799 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 2. Help for "Field Attributes Window" HIDE should mention │ │ that the behavior of │ │ the HIDE attribute on a LIST box is different than on a │ │ field. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3800 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. 50 line mode seems to cause screen formatter (at least │ │ in Generator) to eat │ │ keystrokes. Sometimes it is just sluggish. Other times, │ │ keystrokes need to be │ │ rekeyed to be recorded. │ │ 3. While designing a virtual screen in 50 line mode with │ │ 100 virtual lines I marked a 40 x 78 block of fields then │ │ pressed the up arrow once and the block disappeared! My │ │ machine was then completedly locked up and need to be cold │ │ booted. │ │ cs msg 54401 │ │ R&D (Colvin): So far, I have not been able to reproduce │ │ either of these scenarios. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3801 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/12/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 4. Calling halt() from within a DLL can cause an EXE to │ │ hang fairly │ │ consistently (3 out of 10 times). Tried using this: │ │ restart(procedure that only │ │ returns) to simulate halt() but for some reason that would │ │ also hang. Calling │ │ halt() from EXE only has (so far) never caused hanging. │ │ cs msg 54401 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3802 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 6. "Pulldown Menu Properties" dialog window has an │ │ inappropriate EXPAND │ │ attribute that causes the SHADOW and LOCAL check boxes to │ │ become separated by │ │ 10-20 lines when displayed in 50 line mode. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3803 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Pulldown Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 6. "Pulldown Menu Properties" dialog window has an │ │ inappropriate EXPAND │ │ attribute that causes the SHADOW and LOCAL check boxes to │ │ become separated by │ │ 10-20 lines when displayed in 50 line mode. │ │ R&D: Duplicate of 3802. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3804 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3. Consider reversing buttons on "Button Field Properties" │ │ dialog window to │ │ show WHEN SELECTED first, and WHEN CHOSEN second (i.e., │ │ reverse them). This │ │ more closely mirrors what happens when the application is │ │ running and how the │ │ developer is thinking when designing the application. │ │ DH - I second this suggestion │ │ R&D (Colvin): This was the way it was originally done - I │ │ was told to reverse it to the way it is now. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3805 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Add hot keys to SOURCE buttons on dialog window │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3806 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/12/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Is there a switch to cause screen formatter to use │ │ "pressure sensitive" │ │ scrolling during virtual screen designs? On my system, the │ │ normal auto-scroll │ │ feature makes the screen move so quickly I cannot control │ │ it very well. (If │ │ not, move this under suggestions). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3807 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using NLM6.1c. If you have a btrieve file with the memo │ │ stored in the same file (MEMO=NOTE). You can occassionally │ │ get a Btrieve error 22 by editing the memo field and doing │ │ a GET(file,pointer) on the edited record where the pointer │ │ was from before the edit session. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3809 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Randy Rogers 75730,1337 MSG#:55071 │ │ I have often wanted a way to specify the mode in which a │ │ file is opened within the developer environment. │ │ How about having somewhere to specify such information - │ │ perhaps in an application's global properties. │ │ For doing the 'alias' lookups you could open the alias │ │ files read-only. The main file would be opened │ │ read-many write-one mode. │ │ Regards, │ │ Randy Rogers │ │ Keystone Computer Resources │ │ From Greg_W: I'm not sure if this is feasible or not but I │ │ figured I log it as a suggestion for a future release. │ │ Let me know if you not sure what he is suggesting. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3810 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The column to the right of a list box is visible to the │ │ mouse as part of the list box. This came up as users │ │ reporting being able to complete selects and browses by │ │ double-clicking outside of the list box. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3811 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ During source code generation of a form with several │ │ releationships with cascade; an error window appears. │ │ #IF Scope Stack OverFlow │ │ R&D: Tom has a template fix for this... check with him on │ │ the template batch it will go up in! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3812 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 54485 S8/3.0 Support │ │ 09-Feb-94 13:38:37 │ │ Sb: 3007.102 Report Problem │ │ Fm: Peter Hale 71776,401 │ │ To: 72662,475 │ │ Reports with filters and group breaks may have bad values │ │ in group break fields │ │ on footers due to the fact that the save footer routines │ │ are called for each │ │ record on the primary file. The save footer routines │ │ should be called only for │ │ those records that pass the filter. I relocated the │ │ template code in │ │ REPORT.TPX so the save routines are after the filter/ │ │ selector code and the │ │ report worked fine. │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3813 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you link the Clipper and Paradox drives into the same │ │ app in a non-DLL memory model you get duplicate linker │ │ warnings for _drv_ChkName and _drv_CopyFile. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3814 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 54542 S8/3.0 Support │ │ 09-Feb-94 17:18:46 │ │ Sb: Refer() │ │ Fm: Jeff Moyers 70254,2434 │ │ To: Debby Herman 72662,475 │ │ Debby: │ │ I am having a problem with refer(). When using the mouse, │ │ if I leave an entry │ │ field and move to (click on) a button field, Refer() will │ │ return TRUE every │ │ time, regardless of whether changes have been made. The │ │ value of Selected() │ │ points to the button, the value of Field() points to the │ │ entry field. CUA │ │ screens. │ │ DH I created an example that shows this. See ifle 3814.zip │ │ R&D: This small problem could be seeded deep into the │ │ library, so I'm not going to fix it yet as it may very well │ │ break something more important. I'll fix this as soon as │ │ I'm given the go ahead, though. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3815 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : ?? DateReported : 2/14/94 │ │ Reported In : RevisedDate : 2/14/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This bug needs to be deleted, I locked up when entering it │ │ and can't delete it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3816 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : ?? DateReported : 2/14/94 │ │ Reported In : RevisedDate : 2/14/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This bug can be deleted I locked up again while editing the │ │ memo. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3817 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:54877 │ │ Apart from the screen formatter bug already reported, we │ │ had a couple of instances of the App Generator getting │ │ confused with symbols. │ │ One student created a screen by mistake on a │ │ PullDown procedure. He deleted it by highlighting the │ │ screen button & pressing Del. Ok so far. Then he │ │ re-generated and compiled - an OPEN(SCREEN) statement had │ │ been generated which of course caused a compile │ │ error because there was no screen. │ │ I managed to get rid of │ │ the error by changing the template type to browse and back │ │ again. But obviously an internal flag symbol was not │ │ cleared when the original screen was deleted. │ │ A similar │ │ problem happened with a file template procedure. One of │ │ the students clicked 'Clear file name on Cancel' ON. The │ │ code to do the CLEAR was not generated. I checked the │ │ template code, copied the procedure, did all sorts of │ │ things - but the code would not generate. Eventually I │ │ trashed his procedure, created a new one, clicked on the │ │ option and then the code was generated correctly. So the │ │ symbol was for some reason not being set. │ │ R&D: Tried, and tried, but I just can't do it... can't │ │ reproduce either one of these reported bugs! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3818 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/14/94 │ │ Reported In : 3007 RevisedDate : 2/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports - after going from 3007 to 3007.1 he can no │ │ longer use the brequester instead of btrieve tsr for the │ │ cdd environment. He says that he is getting error 97. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3819 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : List Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:54879 │ │ The LIST template as of 3007.102 appears not to work... │ │ Consider a simple LIST, form combination. The first time │ │ the list is opened, the records are displayed correctly. │ │ REBUILD QUEUE is ON. Add a record, back to the LIST box │ │ and crazy things happen - some or none of the records │ │ display, get messages about DUPLICATE key fields even when │ │ there aren't any etc. │ │ R&D: I cannot get this to reproduce under the parameters │ │ he's specified. Please have the user send a test │ │ application, and/or check operation under 3007.2 templates. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3820 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : File Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:54880 │ │ I'm sure that you will correct this in time, but I thought │ │ I'd point it out... │ │ SUGGESTION │ │ ---------- │ │ Starting on line 198 of FILE.TPX, the following code may │ │ be found │ │ SETPATH(SaveDir) ! │ │ Return to starting path #IF(%DirQueueExists) │ │ FREE(DirQueue) ! │ │ Free the DirQueue memory #ENDIF │ │ FREE(FileQueue) ! │ │ Free the FileQueue memory #IF(%ClearOnCancel) │ │ CLEAR(%SaveFilenameVar) │ │ #<! Clear the filename variable │ │ #ENDIF │ │ DO ProcedureReturn │ │ #<! And leave the Procedure │ │ But ProcedureReturn repeats all this code - kill │ │ all the above lines except DO ProcedureReturn. │ │ ProcedureReturn ROUTINE │ │ #<! return from the PROC SETPATH(SaveDir) │ │ !Return to starting path │ │ #IF(%DirQueueExists) FREE(DirQueue) │ │ !Free the DirQueue memory #ENDIF │ │ FREE(FileQueue) │ │ !Free the FileQueue memory DO │ │ EndOfProcedureEmbed #<! Process the │ │ final EMBED RETURN │ │ #<! END exit the PROC │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3821 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/14/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports-- when using universal browse as a select │ │ template while you are in the list box and choose the │ │ select pushbutton; when button is pressed code doesn't │ │ happen. If you tab to it then press enter all is well. I │ │ do not have a test file. │ │ R&D: Fixed (I believe) in 3007.103(?) template release. │ │ Should be tested for 3007.2 templates. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3822 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : VID │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 MSG#:54909 │ │ When running the debugger, FirstParam = COMMAND('1', 3) │ │ returns a value that is the name of the program that's │ │ running instead of the first parameter. So it's equivalent │ │ to: FirstParam = COMMAND('0', 3) │ │ The '1' used to work in an earlier version (3004 last time │ │ Ichecked) but not in 3007. │ │ This problem only occurs when running the debugger. It's │ │ fine if you run the .exe file from DOS. │ │ From Greg_W: I think this has always worked this way due to │ │ CLAXVID programname %1 │ │ However, it would be nice if COMMAND() somehow detected │ │ debug mode/code. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3823 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you are placing information on a form, after you have │ │ selected DATA, and you choose the field, the program allows │ │ you to move the field prompt around for placement, but if │ │ you press the RIGHT mouse button (or left for that matter) │ │ by accident, the field prompt gets deleted from the screen. │ │ DH User reported this and was referencing the field │ │ itself. I only can see it happen with the prompt. │ │ R&D (Colvin): This is correct - starting in 3007 with │ │ the new mark and drag paradigm, right mouse button emulates │ │ an Escape, while the left mouse button must be clicked │ │ WITHIN the marked area (i.e. the prompt field). Left │ │ clicking outside the marked area says to unmark the area │ │ and start over, which in this case deletes the field (since │ │ it didn't exist in the first place) and finishes the field │ │ add. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3824 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The new GUI is placing thin lines on the screen. This will │ │ only happen a second time if you re-boot the computer. If │ │ you exit the program and try to open the screen again you │ │ will not see the line. │ │ MD: This was fixed, and the sources given to BOBZ to be │ │ placed where he wants them. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3826 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/14/94 │ │ Reported In : 3007 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The laser.ctl has a problem with the okidata printer. When │ │ you get down to the sequences the first tWo listed for the │ │ okidata, 30 7 is the first two numbers. One of them needs │ │ to be 30 ?. where ? is something other than 7. The │ │ problem that this creates is when you go to use this │ │ printer in the report formatter, it grabs the printer │ │ control above it. If you need further info please call me. │ │ R&D: The problem is with incorrectly entered duplicates in │ │ the control file. My suggestion is we fix the CTL files │ │ rather than filter the duplicates, since the CTL files are │ │ incorrect, and really need to be updated anyway. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3827 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ : 54642 S8/3.0 Support │ │ 10-Feb-94 10:15:16 │ │ Sb: _3007.1 SCR Format BUG │ │ Fm: Rob Mousley 100075,772 │ │ To: Debby Herman 72662,475 │ │ Hi Debby, │ │ Consider a field defined in a dictionary as: │ │ Sex STRING(1), Must be in list - 'M F' │ │ Open up a screen, CtrlF, choose the field. │ │ The first option appears, click on Ok, its placed on the │ │ screen ready to be │ │ moved (if you want,) into postion. At this point you │ │ SHOULD press Enter. If │ │ you click anywhere else on the screen with the mouse, the │ │ radio dissappears. │ │ That's bad enough, but if you take to extremes (as one of │ │ my students just │ │ did(!)), │ │ you can cause an XTRACE. I can't get it to happen every │ │ time at the same place │ │ but the formatter definitely gets upset eventually. If you │ │ destroy both the │ │ radio buttons (by clicking randomly on the screen instead │ │ of pressing Enter), │ │ the prompt field is then written as text onto the screen │ │ (sometimes). │ │ Sometimes it just crashes. │ │ R&D (Colvin): Mouse must be clicked within the marked │ │ block (see #3823). I have fixed a bug that occurs when all │ │ radio items are not accepted by clicking elsewhere. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3831 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Kevin P. Chittenden 73564,2056 MSG#:54922 │ │ Print engine problem with ALONE attribute: │ │ It is my understanding that the Alone attribute on a report │ │ section is supposed to print that section on a page by │ │ itself. Is this true? My application seems to add one to │ │ the page counter, but it does not print the title page on a │ │ page by itself. │ │ From Greg_W: I tested this with the orders application and │ │ it doesn't seem to work. The reports band had the ALONE │ │ attribute but it didn't print on a page by itself, instead │ │ the report just started printing on the next line. │ │ Let me know if you need an example. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3829 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/15/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007.1: │ │ On the Browse in the test appliacation, the title in the │ │ list box is getting overwriten by one of the records in the │ │ file. It only seems to happen if there is a Locator. │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3830 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ see 3830.zip for possible rounding problem. also the │ │ variable longfld shows a different value in the debugger │ │ than what shows on the screen. │ │ SF2DAB: I do not know if this is relevant, but I found │ │ that if I debugged this code in assembler mode and examined │ │ the floating point registers just before the call to fist │ │ then the expected value is stored. This is probably just │ │ a side effect of the debugger having to querie the fp chip. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3832 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Andy Stapleton 75110,2467 MSG#:54926 │ │ Well, I Tried it and got the "This Function Not Allowed" │ │ As a Suggestion for next release. │ │ Allow the Free form Formula section to do SET,GET │ │ Functions.... │ │ AnyBody Else have more functions they would like │ │ to ADD... │ │ The reason to add these functions allows the │ │ developer to access the same type of functions your using │ │ in the EBROWSE without having to mantain several file │ │ structures and File Handles ..... │ │ I Think This would be a FANTASTIC │ │ enhancement of the System..... │ │ The TEmplate change would have to │ │ Include a LOOKUP statement and Check to see that the Fields │ │ MATCH..... │ │ LET ME KNOW HOW YOU FEEL AND WHAT │ │ PROBS WE CAN FORSEE │ │ Andy <<Cowboy>> │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3833 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Bayliss 100025,1577 MSG#:55272 │ │ Compiler Reboot problem: │ │ There are two known foibles in this area. │ │ 1)If you DO to a name that is a procedure and not a │ │ ROUTINE.2)If you GOTO into or outof a ROUTINE. │ │ From Greg_W: I know that David_B knows about these │ │ problems but I'm logging them so that others know as well. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3834 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Jung 72466,1526 MSG#:54940 │ │ Start up CDD, select File, New. You should have the screen │ │ showing Application, Database, Text, etc. OMM, pressing │ │ the letter "D" by itself causes the cursor to go to │ │ "Database" (whose hot key is 'b'). Pressing any other │ │ letter does nothing.... The alt+ hot keys are ok. │ │ From Greg_W: I duplicated this situation who knows why it │ │ happens. │ │ Mike: It seems "within the context" of a radio-option set, │ │ pressing the first character of a radio string takes you │ │ to that radio item... even if the first character is the │ │ ampersand (&) character which indicates the Alt-hotkey!!! │ │ MD: I'll need verification from someone with the power to │ │ change this. This works because of some 2.1 │ │ backward-compatibility issues, and, after all, the '&' in │ │ front of the character means the ALT-letter for that radio. │ │ For now, I'm leaving it so as not to screw things up but │ │ will be happy to change it when directed to do so. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3835 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Todd Seidel 72550,3455 MSG#:54941 │ │ Found 2 minor bugs with the 3007 editor. │ │ 1. On both Ctrl/P and Ctrl/K the message at the bottom of │ │ the screen does not cover up the old message. With Ctrl/K │ │ the "Source Code" message on becomes "Press Key to │ │ Definerce Code". You had the same problem earlier with "No │ │ More Occurences" message and this was fixed in 3006 │ │ (or 5?). │ │ 2. Normally you can open a new window by │ │ choosing Alt/W, Change Window, and then select an empty │ │ window. You are prompted for a file to load at which time │ │ you can type in the file name. This way of loading a file │ │ will no longer work if you Press F3 to load a file and │ │ then Cancel that window. After you have canceled that type │ │ of open then using the Change Window will not work until │ │ you load a file using F3 (Open). │ │ BTW this method of loading a │ │ file is much faster (since the directory is not displayed) │ │ then using F3. It would be nice if you could do a quick │ │ load to the next available window. Maybe a Shift/F3 could │ │ be the same as choosing Change Window and moving to │ │ the first empty window. This way if you knew the file │ │ name you could instantly load it. │ │ HTH │ │ Todd Seidel │ │ There is 1 Reply. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3836 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul M. Blais 72103,111 MSG#:55051 │ │ I have found an API BUG. When using the access API call I │ │ find that a protect mode mem model returns a +1 for file │ │ not found. But under overlay mode the function returns a │ │ -1 (as documented). I can deliver an example if required. │ │ I have been using this in conjunction with a control │ │ file to store all the path names to my data files. I have │ │ an external module that is called to verify that all file │ │ paths are indeed valid, exist, or not found. I process a │ │ case statement to count up all the files with each │ │ of these attributes and inform the user to see the sysop if │ │ they are not all found to be valid. In testing I often run │ │ without files so they would be created on the fly. In real │ │ operations I would not want this to go unnoticed so I flag │ │ the error. │ │ In my testing the return status of +1 │ │ (undocumented) winds up in the ELSE part of the CASE so it │ │ is assumed to be an invalid path. When it is fact a valid │ │ path, but the file does not exist. The file does get │ │ created properly and the status changes to OK. Under │ │ an overlay memory model all works properly. Could this be │ │ a leftover from the 3007 INT() bug it appears that the sign │ │ is being lost. I've tried defining the return code from │ │ access as a SHORT and as a LONG with the same results. │ │ I wrote the original │ │ routine under 3005 and it has been working properly, but │ │ now under 3007.102 it do not. │ │ -Paul │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3837 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:55075 │ │ Using 3007.102 standard Browse & Form, I notice that COMMIT │ │ causes POSITION(File) to be cleared. This presents a │ │ problem for the code inserted by the GROUP │ │ %IsUpdateSuccessful such that whenever UpdateMode = │ │ ChangeRecord, UpdateSuccessful always gets set to False. │ │ Using Clarion Driver - consider: │ │ UpdateSuccessful = True │ │ IF POSITION(File) <<<< Never true after COMMIT │ │ IF UpdateMode = DeleteRecord │ │ UpdateSuccessful = False │ │ END │ │ ELSE │ │ IF UpdateMode = ChangeRecord OR UpdateMode = AddRecord │ │ UpdateSuccessful = False │ │ END │ │ END │ │ I suppose this could be a template bug, but I wouldn't │ │ expect COMMIT to have an effect on POSITION. Either way, │ │ something needs to be changed. Douglas │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3838 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using the commmand line editor. If you press Esc whilst │ │ loading a file you will get an XTRACE. I have tested this │ │ under OS/2's DPMI and DOS5 with HIMEM's XMS. │ │ R & D - Due to popular demand - ESC has been removed as an │ │ option to stop loading a file. You may now type ahead │ │ keystrokes. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3839 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Jung 72466,1526 MSG#:55113 │ │ CDD3007.102 │ │ The dictionary editor will allow you to enter a field name │ │ like CUS:ACCOUNT. I thought it would be neat to have a │ │ final field look like INV:CUS:Account (for an invoice │ │ header file) to better reflect that this should match │ │ CUS:Account in a customer file. i.e. IF INV:CUS:Account │ │ = CUS:Account... │ │ Its not exactly clear in the docs whether having more than │ │ one colon is illegal or not (and in fact the templates │ │ generate XXX::YYYYY labels on a regular basis). If having │ │ more than one colon is legal, then the compiler is choking. │ │ If its illegal, then the DCT should reject a field name │ │ containing a colon. --David │ │ There is 1 Reply. │ │ R&D: I did not have any troubles compiling code that had │ │ a field of form yyy:name and calling it the code │ │ with xxx:yyy:name. What does he mean by choke? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3840 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Chuck: The return value from the call to Admin to pick a │ │ field returns the variable without a prefix... however, │ │ add a prefix to the inner group and now a prefix is │ │ returned. Vince. - Please see APP in 3840.zip │ │ Sb: Screen Formatter Bug │ │ Fm: Randy Rogers 75730,1337 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ I have uncovered a small problem with the screen formatter. │ │ Here is how to duplicate the problem: │ │ in a Procedure Properties Data screen create a data layout │ │ like this │ │ GroupA GROUP,PRE('AAA') │ │ GroupB GROUP <-- Note No │ │ Prefix Here │ │ FieldB1 STRING(1) │ │ END │ │ FieldA1 STRING(1) │ │ END │ │ to summarize the above, create a group within a group with │ │ the outermost group having a prefix and the inner group │ │ withno prefix. follow the inner group with another field. │ │ This field will need to be placed on a screen as │ │ AAA:FieldA1. │ │ Now go to the screen formatter and try to │ │ place the FieldA1 on the screen. You can place it there, │ │ but notice the field name is missing the AAA: prefix. This │ │ will not compile with the prefix missing. │ │ Regards, │ │ Randy Rogers │ │ Keystone Computer Resources │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3841 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ please look at 3783.zip. choose the first menu option. on │ │ the browse locate to a specific lastname. now choose the │ │ CHANGE button to modify the record. The field that was │ │ being used for the locator is blank. It seems that │ │ browseaction is blankin the locator field. │ │ R&D: I believe this was fixed with 3007.103 Template │ │ Release. I cannot get this to reproduce with 3007.103, and │ │ A fix in 3007.103 was made in the area of code where this │ │ problem would be located. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3842 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 54837 S8/3.0 Support │ │ 11-Feb-94 02:01:26 │ │ Sb: VIEW bug? │ │ Fm: David Jacobson 74750,3347 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ I've been playing with the Advanced example that was put up │ │ here a couple of │ │ days ago. I've noticed some peculiar behavior with the │ │ View procedure │ │ (README). │ │ Everything works fine in 25 line mode and everything works │ │ fine in 43/50 line │ │ mode but when you switch back from 43/50 to 25, something │ │ breaks. First, the │ │ list box control bars don't behave correctly: clicking on │ │ the bar doesn't move │ │ the text or the list box bar cursor. However, the bar's │ │ arrows appear to │ │ function. Using the horizontal bar tends to cause lockups. │ │ And most │ │ strangely, the entire screen window scrolls once the mouse │ │ cursor reaches below │ │ the third line from the bottom. Moving the mouse below │ │ cause the screen to │ │ scroll up...you can then move it back down by moving the │ │ mouse cursor up the │ │ screen. Very interesting but definitely a problem. │ │ I've tried it with 3007.101, 3007.102, and ST4.1b. I've │ │ tried it Overlayed and │ │ in Protected modes. It all behaves the same. I first │ │ noticed it with the EXE │ │ that was distributed with ADVANC.ZIP │ │ R&D: Fixed in 3007.103 Template Release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3843 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 2/15/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User reports auto-numbering does not work properly on a 3 │ │ component key (auto number on last component). He says │ │ primes are generated correctly, but code does not check for │ │ a match in the second key component │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3844 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 MSG#:55251 │ │ For some reason 3007 has a DISPLAY statement in the │ │ %ScreenEditRoutine group. Right after │ │ of %ScreenField │ │ %ScreenFieldEdit │ │ DISPLAY │ │ This "Display" statement is unnecessary and causes │ │ problems. It's redisplaying the entire screen after │ │ every field embed. If fields are superimposed one on │ │ top of another, it redisplays the underlying field. I │ │ think it should be up to the programmer to put a │ │ Display or a Display(?) into his or her own embed if they │ │ really need the field(s) to be redisplayed. Executing a │ │ Display statement on every field embed is also │ │ inefficient. Besides that, my old programs don't work, │ │ and that should be reason enough.<g> │ │ Barry... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3845 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jake Stockstill 71023,1644 MSG#:55256 │ │ When using a mult-field key and you donot use the first │ │ field of the multi-field key; 1) The program won't compile │ │ 2) The control breaks are improperly coded. BRK:: │ │ fields are not initialized correctly. (The first field in │ │ the key is never initialized; this causes a level 1 │ │ break when each detail record is processed.) │ │ R&D: Fixed in Template Release 3007.103 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3846 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 3007 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When giving a text field word wrap attribute it does not │ │ end up in the code after saving the report structure. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3847 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 3007 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Report Writer │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Give the device a filename. Run the report. It does go to │ │ the file. Go back to the device, on the line in ctrl-o for │ │ device clear it with ctrl-end then choose ok. Now run the │ │ report. It remembers that it is still supposed to go to │ │ that file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3848 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Database Browser │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After pressing ctrl-t to edit a memo, press f1 for help. │ │ you will get the help for the report writer. │ │ MD: Fixed on my end, however a new help ID called DTBDGMEMO │ │ needs to be added to the help file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3849 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 2/15/94 │ │ Reported In : 30073 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : CPD 21 Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Tom, │ │ 3007.103 batch │ │ Form21 template procedure has ABORTTRANSACTION BYTE │ │ duplicated at line 536 of CPD21.TPX │ │ Everything else looks good in CPD21 │ │ Thanks!!! │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3850 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Database Browser │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Is there a posibility of getting word wrap to happen when │ │ you are editting a memo here in the editor. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3851 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A user would like to have embeds around doing lookups. │ │ This is desired for both the forms and browses. He is │ │ aware that he can change his own and has already done so. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3852 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is desirable to have the ability to copy one helpid to │ │ another since the only things that _might_ be different │ │ would be the id itself and the topic. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3854 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/16/94 │ │ Reported In : 3007 RevisedDate : 2/16/94 │ │ Fixed In : Status : Question │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User was try to conditionally compile on the maincode │ │ conditional switch? is this valid: │ │ omit('myterminator',maincode=0) │ │ He was getting a compile error: invalid omit/embed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3855 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When running from Windows the GRAPHICS.EXE (Demo │ │ supplied by Clarion) will result in General protection │ │ error when Linked in protected mode w/ and w/out DLL. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3856 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This is an example 2.1 app where if you import a file into │ │ the CDD dictionary and try to change a field name you will │ │ xtrace. │ │ see file 3856.zip │ │ ts project 2078 │ │ cs id 72425,1402 ed steinberg │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3857 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PS DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1) Enter a Scrren. 2) Press AltE 3) Toggle the Paint so │ │ it is now OFF. 4) Press CtrlM twice. 5) Press ESC and │ │ look at what happened to your nice screen! It full of doo │ │ doo now! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3859 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you have a repeat structure that repeats 13 times for │ │ example, but you only │ │ twelve items filled in, pressing END will cause the │ │ selector to go off the screen. │ │ control-break to continue │ │ see file 3859.zip │ │ ts project # 2080 │ │ cs id 71477,3013 Cindy Cohen │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3860 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ DESCRIPTION: │ │ Converted hlp file for CPD 2.1 using HLPCNV.EXE in CDD │ │ 3007.1. │ │ Ex:> HLPCNV CUSTOMER.HLP CUST30.HLP │ │ Loaded CUST30.HLP into CDD. Used <CTRL> T to test │ │ screens. All were okay. Renamed CUST30.HLP to CUSTOMER.HLP │ │ to test from program. │ │ Ran CUSTOMER.EXE to test help screens. This was also │ │ okay immediately after conversion. │ │ Loaded CUST30.HLP into CDD again and went to screens (ALT │ │ S). Black on black areas at end of lines appeared. │ │ Repainted screens and saved. Renamed CUST30.HLP to │ │ CUSTOMER.HLP to test from program CUSTOMER.EXE. When │ │ pressedF1 for screens that were changed, black on black │ │ boxes were on help screen at end of lines. The parts that │ │ are black on black should be green. These green areas did │ │ display, but displayed outside the borders of the help │ │ screen. When the help screen was cleared (ESC) the green │ │ patches outside the help screen borders was still there. │ │ Created completely new help file, │ │ CUSTEST.HLP with one help screen for │ │ the Customer Key on the entry │ │ screen. This help screen also produced the black │ │ patches inside the help screen and green patches outside │ │ the help screen borders. CTRL T in CDDon this help file │ │ displayed the same patches. │ │ see test file │ │ 3860.zip │ │ ts project │ │ #3081 cs id │ │ 73241.2250 mike johnson │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3861 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ if you go to band properties and set up ALLOW with a │ │ variable and then click on OK. When you come back and edit │ │ the variable is gone. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3863 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Caution these keystroke will produce an XTRACE │ │ Bring up a screen in AppGen. Go to a field and press CtrlF. │ │ AltL to get to the Color selections. Notice what is in the │ │ Listbox. Press AltN (listbox has changed). Press ShftTAB │ │ and arrow down to 2nd Selected line. Press ENTER, ESC, │ │ DownArrow, ENTER and the CXTRACE will occur. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3864 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ all records are printing on a report that has a range limit │ │ see file 3864.zip │ │ ts project #3082 │ │ cs id 71534,2666 │ │ ken c bame │ │ R&D: Fixed in 30072 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3865 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/16/94 │ │ Reported In : 3007 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Page Of template using the chckbook example the payee has a │ │ multipage page and page of when I get to a field hitting │ │ altq -- the letter q gets typed into the field. Moreso... │ │ if you were to have a display only field with a prompt, │ │ and decided to hit the hotletter for that prompt that │ │ particular letter would get typed into the field you │ │ are on. Call me if you need further info. │ │ R&D: Fixed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3866 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion for extra functions to be added for clipper key │ │ expressions: TRIM, ALLTRIM, LTRIM, RTRIM, UPPER │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3867 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:55318 │ │ The LRM 12-10 states that POINTER(Queue) returns a LONG │ │ specifying the entry number of the last Queue entry │ │ accessed by ADD or GET. │ │ After reading this, I would expect that the │ │ following test would always display the same record from │ │ the queue buffer after an ADD or GET: │ │ PROGRAM │ │ Queue QUEUE │ │ Number LONG │ │ END │ │ QueuePointerAdd LONG │ │ CODE │ │ LOOP I# = 1 TO 20 │ │ Ptr = RANDOM(1,1000) │ │ ADD(Queue,+Number) │ │ QueuePointerAdd = POINTER(Queue) │ │ SHOW(I#,1,Number,@n3) │ │ SHOW(I#,10,QueuePointerAdd,@n3) │ │ GET(Queue,QueuePointerAdd) │ │ SHOW(I#,20,Number,@n3) │ │ END │ │ ASK │ │ RETURN │ │ Of course the result is not as I │ │ expected or else you wouldn't be getting this message. What │ │ should be noticed is after ADD(Queue,+Number), │ │ POINTER(Queue) always returns the previous number of the │ │ highest queue entry. Thus, the value is always increasing │ │ and never shows accurately for an entry added somewhere in │ │ the middle of the queue. Douglas │ │ From Greg_W: I created an example file called 3867.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3868 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 3/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : View Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:55355 │ │ The View Template is changing the Video mode if you │ │ come from a graphics screen. Example: If your in SVGA mode │ │ and you call a View procedure when you return your in cga │ │ mode. │ │ R&D: Cannot reproduce in 3009 template set. The code to │ │ handle this was repaired in the 3007.10x template releases, │ │ and was possibly repaired. Will call the user to check if │ │ problem exists in 3007.200 templates. │ │ R&D: User reports problem fixed in 3007.2 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3870 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Goto hotkey procedures embedded source window. Although │ │ the screen formatter is dimmed and not allowed in this │ │ area, i can type in a screen structure and hit ctrl-f. │ │ This will biring up the screen formatter. I can then save │ │ my screen and the code gets written out. I then can save │ │ the embedded source window and go back to the "Insert │ │ procedure call" window. Next I click on OK and am brought │ │ to the Hotkey Procedure Screen - I now choose EXIT and I am │ │ presented with a clarion runtime halt - Message: Pop screen │ │ w/o push, code 0 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3871 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/16/94 │ │ Reported In : 3006 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Reported by user -- When using VPON with DRAWLINE or XYAXES │ │ Some mystery lines are being printed. The line style is │ │ determined by the first drawline or xyaxes command issued │ │ after VPON. Some later commands override and erase the │ │ ghost lines. To see the problem, you would need to be │ │ printing to a postscript printer. │ │ See file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3872 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/16/94 │ │ Reported In : 3006 RevisedDate : 2/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ VPon and the DRAWICON │ │ On a postscript printer, The icons that are printed do not │ │ corespond to the ones that are on the screen. #6 and #7 │ │ are duplicates. see file 3871.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3873 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the list box formatter, place a field 10 character │ │ field so that the end of it is at character 253 of the list │ │ box. Now while in insert mode, move two characters to the │ │ left and place a 10 character field. And just for │ │ demonstration do this one more time. You should find that │ │ the first field that you placed is now out past 255. When │ │ pressing ctrl-x to exit an xtrace will occur. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3874 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/17/94 │ │ Reported In : 3007 RevisedDate : 2/17/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the ORDERS.APP that is shipped with CDD, when the │ │ BROWSEITEM screen and UPDATEORDERS screen are setup to be a │ │ virtual screen of 50 rows by 80 columns and the application │ │ is then compiled and linked, this screen will then freeze │ │ when you try to access them. │ │ Also, if you then try to go back and set the screens to 25 │ │ by 80, it still goes back to 50 by 80. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3875 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/17/94 │ │ Reported In : 3007 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When an update procedure(a form) has a pulldown and the │ │ active field is a string, when ALT+R is pressed, where 'R' │ │ is the hot letter for the pulldown, then the ESC key is │ │ pressed, the hot letter for the pulldown is inserted in the │ │ current field, this only happens if there is already │ │ something in the field, if the field is blank, it doesn't │ │ happen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3876 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ TABLE21 and FORM21 is causing an error during compilation. │ │ 'Cycle statement must be within loop' and 'break statement │ │ must be within loop'. │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3877 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Response │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Reported by user ; In the formula editor, if you decide to │ │ not use the expression generator, you will be typing in the │ │ memo yourself. Since that field is a memo... If I have a │ │ long string that I am concatenating, due to the word │ │ wraping I will get a | in the string and it will word wrap │ │ to the next line. This will generate a compiler error. │ │ R&D: With the current way memo fields with word wrap │ │ operatethe bound on the length of a constant string is the │ │ length of one 'memo' line in the free-format text field (52 │ │ characters excluding the enclosing quotes). If the │ │ user wants a longer string then catenation of strings, │ │ each no longer than one line, should be used. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3878 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Dictionary with btrieve file that has nested groups. Locks │ │ up the database manager. │ │ see file 3878.zip │ │ see also 3878a.zip - dictionary that works and one that │ │ doesn't. │ │ Scott this may be a database manager problem. If I created │ │ the file and then exited the program I could then add │ │ records to the file through a program but not in database │ │ manager. The user indicates that he can't add records. │ │ ts project # 3077 │ │ csid 76535,1712 Tom Paulson │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3879 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When you issue a CHANGE(), and either the field value │ │ passed is 0 (because it might be called as CHANGE(?,...), │ │ and there is no current field, or the current field is not │ │ an entry field (like a button), CHANGE bombs the system. │ │ In CLAVID, if field() is 0, you get a Extended Memory │ │ exception. If not in CLAVID, you get an "Invalid Screen │ │ Structure" Runtime halt. See Dave B for an example of this │ │ happening. │ │ I understand that in either case these faults are caused by │ │ coding errors, but they should not dump the system. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3880 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CHANGE() │ │ When the second value passed to CHANGE() is longer than the │ │ field that the value is to be placed in, the CHANGE │ │ overflows to the next field(s). In other words, if you │ │ have two 10 character string entry fields, and you do a │ │ CHANGE(1,'X{20}'), the first field gets 10 Xs, and the │ │ second field gets 10 Xs. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3881 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CHANGE() │ │ It was my understanding that CHANGE() is supposed to update │ │ the USE variable and the screen display. I find that it is │ │ necessary to issue a DISPLAY after a change for the new │ │ values to be displayed. If CHANGE is supposed to be │ │ changing the screen variable, then a DISPLAY should be │ │ unnecessary. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3883 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/17/94 │ │ Reported In : 3007 RevisedDate : 2/21/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when an app tries to open a dct that is already being used │ │ you will get the warning screen - after clearing this │ │ screen you will get the warning that there is an A$$ file │ │ out there. There is no way to gracefully exit if the │ │ dictionary is already being used. │ │ R&D: I have called and left a message with Anstine │ │ Information Solutions... still waiting for more │ │ information. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3884 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 2/17/94 │ │ Reported In : RevisedDate : 2/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This program will not compile using the extend Dll model... │ │ (it will work in all other models!!) │ │ PROGRAM │ │ MAP │ │ MODULE('TopSpeed API Function') │ │ DOSFINDCLOSE,NAME('DOSFINDCLOSE') │ │ . . │ │ CODE │ │ DOSFINDCLOSE │ │ RETURN │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3885 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Incremental locator │ │ Locator gets selects if user backspaces all the way to the │ │ "beginning" of the field while they are in the list box. │ │ Example: In this bug program, in several instances, I │ │ backed spaced to get to the "beginning" of the locator │ │ field and I assumed that the list box will scroll to the │ │ beginning of the scrolling data list. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3886 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 MSG#:55605 │ │ In CDIR if you press the Grey + it would put the filename │ │ of the currently highlighted file on the command line │ │ unless you had files marked, then it would put %N.%E on │ │ the command line. This behavior has not carried over to │ │ CSHELL. At least on my computer <g>. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3887 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is not indicated anywhere in the help that CTRL-T │ │ activates tag in the CSHELL. │ │ **Note: 2.1 users are used to CTRL-M. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3888 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/17/94 │ │ Reported In : 3007 RevisedDate : 2/17/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Strange occurance in a memo field. For an example: look at │ │ the memo in problem # 3877. where the word operate is at │ │ the far right and not on the next line. Then when you │ │ select the memo, you will see it in both places. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3889 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Response │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Leschak (CompuSyste 71461,471 MSG#:55589 │ │ i have found the following piece of code in the │ │ FORMGRPS.TPX file and questioned is correctness: │ │ #ENDIF │ │ #SET(%RelationString,('['&FilePre&'u'&RelationPre&']')) │ │ #SET(%ParentPre,('['&%FilePre&']')) │ │ should it be: │ │ #ENDIF │ │ #SET(%RelationString,('['&%FilePre&'u'&%RelationPre&']')) │ │ #SET(%ParentPre,('['&%FilePre&']')) │ │ the │ │ above lines has many occurences in FORMGRPS.TPX. │ │ also, │ │ #SET(%TempYear,(SUB(%ProgramDateChanged,7,4))) │ │ and │ │ #SET(%TempDate,(RIGHT(%ProgramDateChanged,9))) │ │ both return null to the destination symbol, what am i doing │ │ wrong? │ │ jsl │ │ 1. Although problem 1 is wrong in the template, it has no │ │ effect on generated code. Generator does not require the % │ │ symbols. │ │ 2. %ProgramDateChange is no longer supported in the │ │ Generator. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3890 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Response │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick Weiss 71764,1312 MSG#:55591 │ │ The Repopulate Source Moduled with the "Static Procedure │ │ Tree" option seems to work...to a point. │ │ I have an app with about 100 procedures. When I use this │ │ option, about the first 20 modules seem to be grouped │ │ logically, and the remaining 80 are strictly alphebetical │ │ as before. │ │ PS the Procedures per Module seems to be ignored │ │ too. I have it set to 3, but some moduled have 5 or 6 │ │ procs in them. │ │ R&D: 1. The user may need to select the move from user │ │ defined procedures checkbox. │ │ 2. Optimizing with 3 procedures per module really │ │ doesn't make too much sense and is just used as a │ │ guide to optimization, not a rule. User should │ │ set procedures per module up to more like 10 to │ │ realize any potential benefit. │ │ The optimization attempts to reorganize based on a "longest │ │ call path" method. That is, all procedures on the longest │ │ call paths are grouped together based on the prediction │ │ thatmost program activity will occur within these │ │ procedures sets. (Static analysis is only a best guess │ │ based on some heuristic...) The method tends not to │ │ optimize single procedures called only by one other │ │ procedure and may arbitrarily place these procedures (ie. │ │ adds them to a selected module). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3891 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/17/94 │ │ Reported In : 30072 RevisedDate : 2/18/94 │ │ Fixed In : Status : Tested/OK │ │ │ │ Section : DOS Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The supplied test program does a create(file), no error is │ │ posted, but the file is NOT created. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3892 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Uwe Bornholdt 100114,2105 MSG#:55611 │ │ I have found a problem with the Copy command through a │ │ programming error in OPTIONS.CLA. │ │ Take a look at a code snippet from the SAVEFILE │ │ procedure │ │ OPEN(Ini) │ │ ! Check for existence (assume TEST.INI) │ │ IF ERRORCODE() = 0 │ │ ! Check for file exists x = INSTRING(Namestr,'.') │ │ ! Look for period (always 0) IF x = 0 THEN x │ │ = LEN(CLIP(Namestr)). ! Not found? Put at end │ │ Bkpstr = SUB(Namestr,1,x-1) & '.BAK' ! Create │ │ backup name (Bkpstr = 'TEST.IN.BAK') │ │ CLOSE(Ini) │ │ ! Close file COPY(Ini,Bkpstr) │ │ ! Copy ???.INI to ???.BAK END │ │ CREATE(Ini) │ │ ! Zero current file IF ChkError() THEN │ │ RETURN(0). OPEN(Ini) │ │ ! Open new INI IF ChkError() THEN │ │ RETURN(0). │ │ The Copy command trys │ │ to copy TEST.INI to TEST.IN.BAK. The COPY command returns a │ │ errorcode(). So far so good. But │ │ the following create will return a sharing vioalation │ │ errorcode (only if have loaded │ │ SHARE or running under OS/2, in plain DOS this is not a │ │ problem). So it │ │ looks like the Copy command don't close the source file │ │ during a failure. │ │ The code of OPTIONS.CLA should be changed to: │ │ OPEN(Ini) ! Check for │ │ existence │ │ IF ERRORCODE() = 0 ! Check for │ │ file exists x = INSTRING('.',Namestr) │ │ ! Look for period !!**CHANGE**!! │ │ IF x = 0 THEN x = LEN(CLIP(Namestr))+1. ! Not │ │ found? Put at end !!**CHANGE**!! │ │ Bkpstr = SUB(Namestr,1,x-1) & '.BAK' ! │ │ Create backup name CLOSE(Ini) │ │ ! Close file COPY(Ini,Bkpstr) │ │ ! Copy ???.INI to ???.BAK END │ │ CREATE(Ini) ! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3893 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After Importing a 2.1 Cookbook.App during source code │ │ generation an error appears: Must define a range value. │ │ Also, during compilation the error: Duplicate data label: │ │ ABORTTRANSACTION appears. There is a local range value in │ │ the table but not the PRNT_RECIPE ERROR. │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3894 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard M. Bri~linger 100120,1622 MSG#:55618 │ │ Hello, I have a problem with BROWSE: (Cla 3007.102 + GUI + │ │ Extender) In a big APP, I have 4 browse-Routines for one │ │ file (Address) These 4 Browse-Routines have one common │ │ update procedure (UpdateAddress) Now, I select a record │ │ with one of the 4 browses and press Enter to change the │ │ selected record. On the Form, some or all fields that are │ │ part of a key get wiped out. As far as I found out with │ │ Debug, the fields get cleared in the browse-procedures and │ │ not in the form. Has somebody had the same problem? Is this │ │ a known bug? If so, I there a code-fix available? │ │ From Greg_W: Another user reported that this has something │ │ to do with having a locator on the browse. He said when he │ │ deleted the locator all field showed up on the Form. │ │ I ask for an example if he could upload one. │ │ R&D: Fixed in 3007.2 template release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3895 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/17/94 │ │ Reported In : 30072 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The R.F. is adding an extra block char to a string field │ │ @s10. See the example its easier than trying to describe. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3896 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/17/94 │ │ Reported In : 30072 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A report structure w/out a label on the detail or the field │ │ within the detail causes a xtrace. Looks like an assign │ │ fields problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3897 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: GLENN HARDIN 72611,1410 MSG#:55640 │ │ Give us the capability to assign our chosen keystroke │ │ combinations for the various actions throughout EDITOR and │ │ the rest of the Clarion environment. ..............Happpy │ │ Programming...Glenn │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3898 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When a list box has less than a full page of items, and you │ │ do a SELECT(?List,X), where X is a value less than or equal │ │ to the number of records in the listing queue, the list box │ │ does not display the full number of records, with the │ │ selected record highlighted. Instead, it shows only the │ │ selected record, and any items following that item. It │ │ should display all of the queue items. │ │ If a listing queue does not have enough records to fill the │ │ list box, all records should always be displayed. │ │ If a listing queue has enough records to fill the list box, │ │ at no time should the list box have empty lines. │ │ R&D (Tom Moseley): Erroneous report. Wrote small test │ │ suite and problem does not reproduce. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3899 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Enhancement │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:55657 │ │ I am trying to Import a module from one APP to another, │ │ when you select IMPORT from the Edit menu, Module exists │ │ but is disabled. The Import help screen says to "enter the │ │ name of the module to copy". │ │ I can't get the module copy menu option to enable. │ │ I do all my development in a testing app, once │ │ tested, I import into its final APP, this works extremely │ │ well, reduces the risk of corrupting the production apps │ │ from auto-reboots, system hangs etc while allowing for a │ │ very controlled method of putting subsets of │ │ procedures into production while many other procedures can │ │ still be in testing. Plus significant time savings in │ │ compile/testing a very small app. │ │ This worked fine until │ │ I needed to put a queue definition into a module (did not │ │ want global because these are month end reports and the │ │ entire module is generally run only once a month). Before │ │ I started I had checked that the capability was │ │ there to import a module, but it is my fault that I didn't │ │ test before I built all these module variables. I had to │ │ rekey the module variables in the final APP. │ │ This is │ │ definitely a BUG report, at the very least the help screen │ │ should be changed to say Reserved for future use as does │ │ the Import Global Variables. │ │ Second part of the problem is that when entering Global │ │ Variables, module variables or local variables in the │ │ editor that is used only allows direct keying or coping │ │ from another field in THIS section ONLY. │ │ Jerry L. Petri │ │ Practical Computing Group │ │ R&D: This is intended as a future enhancement... the help │ │ will be changed to reflect this until the time it is │ │ implemented. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3900 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Dave Cohen 70431,132 MSG#:55705 │ │ The ROWS() function with a report structure using SUPPRESS │ │ does not work. The SUPPRESSed lines are not included in the │ │ count, whether or not they are blank. This was reported │ │ earlier - I assume it just didn't make it into 3007.1? │ │ -dave cohen │ │ R & D - Please send an example of this - I can not │ │ reproduce! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3901 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 MSG#:55801 │ │ Want a quick way to cause a protected mode app to XTRACE │ │ when a screen is opened ? Then have the queue that a list │ │ box uses have a record length of 254. │ │ Fred │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3902 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/18/94 │ │ Reported In : 3007 RevisedDate : 2/18/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ help i.ds. If the user enters 'HELPID for a fields Help │ │ ID on a Browse, after doing a Make and Run and realizing │ │ the error, you can't go back and edit the screen to fix it. │ │ All the other options on the Procedure Properties screen │ │ is availible except the SCREEN button. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3903 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Child Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Release 3007.104 │ │ Is it valid to get rid of the delete button? Template help │ │ needs to be updated to tell which fields/buttons are │ │ required and which ones can be deleted. │ │ Suggestion: User would like to be able to get rid of the │ │ delete button? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3904 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ SETPATH needs to handle a trailing backslash! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3905 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The @N picture token has problems with rounding: │ │ Example file: 3905.ZIP │ │ var1 = 0.47 │ │ show(1,1,var1,@N6) ------ 0 │ │ var2 = 1.47 │ │ show(2,1,var2,@N6) ------ 2 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3906 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/18/94 │ │ Reported In : 3007 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The RECLAIM attribute is NOT supported by the file driver, │ │ howver, when you select the Clipper Driver the RECLAIM │ │ Attribute IS ENABLED! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3907 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ As told to me by Tony "No Errors" Kirk │ │ From w/in AppGen bring up an Screen that has buttons on it. │ │ CtrlF on the Button. Press one of the available Source │ │ buttons. Now that you are in the Editor, open a Source │ │ file that has a screen in it. Find the Screen and press │ │ CtrlF. Exit that Screen, Close the Source windows, and │ │ press Esc to get back to the Original Screen. Notice the │ │ "BigRedWindow!" Clarion Runtime Halt Message: Pop Screen │ │ w/opush │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3908 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using the first set of epson printer controls, place │ │ emphasize on and bold on next to each other. Save the │ │ report procedure and the go back to the report. The second │ │ control is gone. │ │ R&D - Which epson printer? I used the first one in the list │ │ and had no problem with the above steps. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3909 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/18/94 │ │ Reported In : 3007 RevisedDate : 2/21/94 │ │ Fixed In : Status : Enhancement │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the formula generator does not seem to be aware that │ │ strings are dimmensioned internally. │ │ R&D: This will be enhancement to a future version. There │ │ are several implications here which need to be worked out. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3910 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the file pulldown there is a Printer Setup and Print │ │ WorkSheet. This is not consistant with the rest of the │ │ environment. Example: The Procedures Worksheet screen's │ │ File Pulldown has Print first and Printer Setup second. │ │ Notice help has Printer Setup first and Print WorkSheet. │ │ Why not just Print, as the procedure Worksheet states. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3911 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 2/18/94 │ │ Reported In : 3007 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CHANGE(SELECTED(),VALUE) will cause unpredictable things │ │ to happen if a field is not selected. It will cause the │ │ debugger to hang if you have not linked the program in │ │ protected mode. It will GP if it is linked in protected │ │ mode. This syntax of CHANGE() is used in the Validate │ │ template. │ │ MD: Fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3912 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ File shows problem of ACCESS returnign a +1 for file not │ │ found instead of returning -1. Problme only occures under a │ │ protected mode model. │ │ file 3912.zip │ │ ts project 3097 │ │ cs id 72103,111 Paul M. Blais │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3913 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Sample program and instructions to demonstrate corrupt key │ │ with clarion filed driver with a DUP attribute on a key. │ │ file 3913.zip │ │ ts proj3098 │ │ csid 73021,2215 rodney viessman │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3914 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suppress line if blank when chose in the report formatter │ │ does not get generated in the code after saving the report. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3915 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports -- Special characters in foriegn Languages │ │ cannot be used as hot letters. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3916 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user -- ÅÄÖ these characters to not make │ │ anything happen in a locator since they are ascii │ │ characters greater than 127. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3917 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/19/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Randy Rogers 75730,1337 MSG#:56014 │ │ The same hot key is used for cOlors and Ok in the help │ │ system 'Update Help List Box' dialog. Most other places │ │ 'L' is the hot key for color. I suggest that this screen │ │ be changed accordingly. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3918 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/19/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jeff Jones 72144,3241 MSG#:56155 │ │ If PACK is used on files with over 32768 records, the │ │ resulting file will have 32768 records. All other records │ │ are then lost. I have two files that have over 32768 │ │ recordsthat are part of a 14 file database. Both files had │ │ exactly 32768 records after the completion of the PACK │ │ command. I started receiving "Record not found" messages │ │ after executing PACK. I am using 3007.1. │ │ From Greg_W: I requested an example if he has │ │ one. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3919 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/19/94 │ │ Reported In : 30071 RevisedDate : 2/19/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Request by user: It would be helpful if CDD could │ │ incorporate its own QBE. It is just a suggestion. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3920 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 2/21/94 │ │ Reported In : 3007 RevisedDate : 2/25/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Editor will not take you to an error if it is in an │ │ Embed that was generated by the app generator. It WILL │ │ work if you are in the app generator. │ │ Dave: │ │ This is due to the fact that from the editor I am still │ │ getting embedded source names instead of CLA file names. If │ │ I were given a switch for the compiler to tell it to │ │ renumber the errors for editor vs generator this could be │ │ handled. │ │ Thanks - Lisa ( R&D at Clarion ) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3921 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Help Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard M. Bri~linger 100120,1622 MSG#:56314 │ │ I think, a SEARCH button in the help system would be very │ │ useful to allow the enduser to search for the occurence of │ │ atext in the help text. thank you. Richard M. Brisslinger, │ │ Tutzing, Germany │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3922 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:56444 │ │ Following are 3 examples which the Universal Browse does │ │ nothandle but the Validate does. │ │ Example 1: │ │ You have a Property (parent) 1:many Appraisal (child), │ │ the task is to place the appraisal file on the screen and │ │ let the user select property at run time from an input │ │ field on the universal browse. The Property_ID is on both │ │ files and is the relationship field in appraisal as a "Must │ │ be In File". │ │ The browse is range limited by │ │ appraisal:property_id (property_ID is internally │ │ generated long(@n_5), the user cannot touch). Place the │ │ appraisal:property_id in the screenbefore the ?List, in the │ │ when completed code BR_property which is a universal │ │ browse to validate the propery_ID (to the user this is │ │ property number that I control). The │ │ Appraisal:property is defined as "must be in file" as a │ │ many:1. The BR_PROPERTY is a striped down universal browse │ │ with the Change, Insert & debutton removed and all other │ │ files removed from the normal browse that has many related │ │ hotfield displays. After all the purpose is to simply │ │ selecta property. │ │ Since I am not in a form, keycode() never gets set │ │ to SHFTENTER, the browse displays the list table with │ │ select disabled, pressing enter does select the button │ │ (real problem), but nothing is returned. If I hand │ │ code setkeycode(SHFTENTER) before the BR_PROPERTY, │ │ the browse displays the list table with select enabled & │ │ either enter or mouse/key press on select will select the │ │ record, remember I am not in a form, nothing is in │ │ the appraisal:property_id. I I hand code │ │ SETKEYCODE(SHFTENTER), BR_PROPERTY, APPRAISAL:PROPERTY_ID = │ │ PROPERTY_ID, display(?appraisal:property_id) it │ │ will work. If I simply put VA_property (to a validate │ │ template) in the when completed, all the actions will │ │ be completed. In either caseI need to add a select(?list) │ │ for the filter to work or mouse press on the list table. │ │ Example 2: │ │ Each user has a default │ │ printer assigned, but on the redirectreport I provide │ │ the abilty to allow to temporarily override using a local │ │ variable, the user can either type in a new printer name │ │ or just overtype one character so that validate doesn't │ │ match and provides a list of printers to choose from. (In │ │ reality I put a down-arrow button in front of the field │ │ so the user can click this clears the printer name │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3923 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ go into screen properties and change physical and virtual │ │ screen size to 30x80 and click ok. When you are back at │ │ the screen, go back to screen properties and change the │ │ physical screen size from 50 to 25 and save. When you are │ │ back at the screen, save the screen. You will have ascii │ │ characters all over your screen when you get back to the │ │ procedure worksheet. │ │ Mike: The problem here seems to be related to having a │ │ LOADBORDER in effect, then switching among various text │ │ modes. Run file 3923.ZIP for example. │ │ MD: Fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3924 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This is an example program to show the affect of IMPLICIT │ │ vars in ROUTINES of memory. │ │ Reply from DAB in the Clarion forum │ │ #: 56548 S9/3.0 Discussion │ │ 19-Feb-94 14:26:51 │ │ Sb: #56452-#*WARNING* │ │ Fm: David Bayliss 100025,1577 │ │ To: Nick Van Eldijk 71613,544 (X) │ │ Nope, I just checked, it is a compiler bug. │ │ *** If you have an implicit variable _only_ used inside a │ │ routine memory allocated for it is _not_ de-allocated on │ │ procedure exit. This memory is allocated on _procedure_ │ │ entry not _routine_ entry. (Implicits 'created' in one │ │ routine are visible to all routines which is how the │ │ problem comes about in the first place). *** │ │ The problem is now fixed and will work its way through in │ │ due course. │ │ The reason in appears 'OK' in the extender model is that │ │ the leak is really quite small and therefore the extender │ │ copes with it. │ │ DAB │ │ See test file 3924.zip │ │ TS proj 3099 │ │ cs id 72144,3241 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3925 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/21/94 │ │ Reported In : 3007 RevisedDate : 2/25/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007.1 =- in a report defining a total in the app gen after │ │ copying and renaming the field he gets a gpf │ │ Dup of Bug 3948 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3926 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Example file from Barry McClure showing bug with PUT in │ │ Btrieve driver. │ │ file 3926.zip │ │ csid 75170,110 │ │ ts proj3100 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3927 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Database Browser │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Example file showing bugs in the Database Manager │ │ file 3927.zip │ │ ts proj3101 │ │ cs id 75170,1100 Barry McClure │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3928 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/21/94 │ │ Reported In : 30072 RevisedDate : 2/25/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Change the syntax in any template to force a template │ │ error. Load an example Application from │ │ C:\CLARION3\EXAMPLE and while the templates are being read │ │ in and error will appear. Press enter to correct the │ │ template. Now, press the EscKey, 'Save file' will appear │ │ without a file name in that field. Press Enter to save, │ │ 'Path Not Found'. Note: The example file is in a different │ │ directory than the template. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3929 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ field() and selected() return erroneous results when │ │ marking a checkbox │ │ see 3929.zip │ │ What should selected() and field() return? Should clicking │ │ on the checkbox complete the accept statement? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3931 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/21/94 │ │ Reported In : 30072 RevisedDate : 2/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : BASIC Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RECORD DEFINED AS ONE FIELD STRING(4000), ON ADD(FILE) WILL │ │ CRASH SYSTEM. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3932 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : ASCII Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ copy statement is returning access denied if the file is │ │ not found. See example file: 3932.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3933 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Paradox Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Example of Paradox file created by Paradox with a record │ │ declaration created by pdxrec. Return invalid key file. │ │ Seems to have to do with secondary key files. │ │ see file 3933.zip │ │ csid 72614,2330 │ │ tsproj 2873.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3934 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/22/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Nick Van Eldijk 71613,544 MSG#:56517 │ │ After importing an encrypted 2.1 file the owner ID is │ │ properly set but the 'encrypt-switch' is not set. Which │ │ causes a (47) invalid record declaration error when trying │ │ to read the file. CDD 3007.104 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3935 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/22/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Nick Van Eldijk 71613,544 MSG#:56520 │ │ Browse 3007.104 with locator: │ │ In a _CUA_ screen, if the Listbox is selected, you can only │ │ use <ShiftTab> to go to the last Button. Forward 'Tabbing' │ │ only switches between locator and Listbox. │ │ In non_CUA you can't get to the Buttons at all with <Tab> │ │ or <ShiftTab>. │ │ From Greg_W: I tested this using the Product Browse in the │ │ Orders application and it did do what he is reporting. │ │ R&D: The locator needs to have a blanking picture (@n3b). │ │ In Non-CUA, Tab no longer completed fields (fixed in │ │ 3007.2) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3936 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/22/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when in module view press enter on a module. The source │ │ button here is ALT-s where on procedure properties ALT-u is │ │ used. Since everybody has used the alt-u in procedure proc │ │ more can we change the other source button's hot letter. │ │ R&D: It seems the standard is going towards Alt-S where │ │ possible... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3937 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/22/94 │ │ Reported In : 3007 RevisedDate : 2/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007.1 reported by user -- run in protected mode -- it │ │ returns a runcode of 9 -- machine with 8megs of ram -- what │ │ is runcode equal to 9 ...if it has a meaning │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3938 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/22/94 │ │ Reported In : 30071 RevisedDate : 2/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Damon Endicott 70712,1247 MSG#:56624 │ │ This is a rare bug. When Converting a file from │ │ Dictionary, my OWNER code began with a %% . The Convert │ │ File Spec stripped the first % off the OWNER spec. The │ │ %%'s were handled fine in the actual APP. It was only in │ │ Gen'ing the convert spec that the first % was │ │ stripped. The error returned was "Invalid File". │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3941 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/22/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Memform21 Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 MSG#:56675 │ │ Found a bug in CPD21.TPX in MemForm21. In the CASE │ │ FIELD() inside OF ?Cancel there is a GET(%Primary,0). │ │ This will cause a compile error if you do not enter any │ │ files under the file button. I changed it to │ │ #IF(%Primary <> %NULL) │ │ GET(%Primary,0) │ │ #ENDIF │ │ R&D: Fixed in 3007.2 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3940 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 2/22/94 │ │ Reported In : 3007 RevisedDate : 2/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you do a SKIP(file,n) where n>1 and are doing file order │ │ processing, what actually is performed is a SKIP(file,n-1) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3942 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 2/22/94 │ │ Reported In : 30071 RevisedDate : 2/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Here is a test app showing problems with multi component │ │ reports. One with 1 group break breaks incorrectly. │ │ One with 2 group breaks, lastname/firstname breaks on every │ │ record even though there are 3 records with the same first │ │ and last name. Also on this report the firstname prints │ │ the same data for every record in the report. │ │ see file 3942.zip │ │ R&D: Finally (phew) found that bug. Fixed in 3007.2 │ │ templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3943 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 2/22/94 │ │ Reported In : 3007 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RESET(key,pos)/PREVIOUS/PREVIOUS where pos is the position │ │ string for the first record does not return an error if the │ │ key is built on a field with Clarion data type REAL. This │ │ does work if you use the alternate @N string picture to │ │ declare the field │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3944 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 2/22/94 │ │ Reported In : 3007 RevisedDate : 3/10/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Memory is corrupted when you get a record who has a memo │ │ pointer field of type LONG. This does not happen if you │ │ use the alternate STRING(10) format. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3946 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 2/23/94 │ │ Reported In : 3007 RevisedDate : 3/03/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When you run a report that has a fairly restricted │ │ filter, it is hard to know if the report is running, or if │ │ you have hung. In 2.1 R/W, there was a "Formatting Report" │ │ flashing prompt, and a incrementing record counter. This │ │ would nice to have in this version. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3947 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 2/23/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : DBase III Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ DUPLICATE(key) returns 0 when the record will be a │ │ duplicate. Driver returns errorcode 40 Duplciate key. │ │ R&D: My test code shows the driver behaving correctly. Do │ │ you have example code? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3948 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/23/94 │ │ Reported In : 30071 RevisedDate : 2/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:56697 │ │ We've had a number of reports of people crashing the 3007.1 │ │ report formatter - by copying total fields into grand total │ │ bands etc. │ │ Try copying some total fields between bands of different │ │ types... │ │ Fm: Arthur Svensson 71554,3162 │ │ I can produce a GPF in a Report procedure at will. To │ │ reproduce this create a Total (SUM) at a BreakFooter. Then │ │ copy this field to the Grand Totals band. Pull a ^F to edit │ │ the field & change its name to avoid the dreaded Duplicate │ │ Label error. │ │ It turns out that the original Total field is ALSO renamed │ │ to the Grand Totals field name. │ │ If you return to the Report formatter and attempt to delete │ │ either/both of these fields or delete either/both report │ │ bands you will crash. │ │ Seems to me this undocumented feature was reported some │ │ months ago. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3950 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/24/94 │ │ Reported In : 30072 RevisedDate : 2/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Situation: User has an application using a styles file. │ │ User issues a setcolor and paint command to │ │ color an entry field if the entry field is │ │ negative. │ │ Instead of only affecting the single entry │ │ field, the color "overwrites" the style │ │ color, resulting in all entry fields being │ │ given the new color. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3951 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/24/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After DELETE(file), position(file) returns a value. This │ │ has serious ramifications in the template code, as well as │ │ any existing code that people use the new drivers for, and │ │ should (in my opinion) have a very high assigned severity. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3952 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/24/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After PUT(file) fails because of duplicate key values, │ │ DUPLICATE(key) returns a value as if an ADD(file) were │ │ taking place, rather than a PUT(file). The result is that │ │ after a PUT in a form that fails because of duplicates, all │ │ of the keys that are autonumbered report (falsely(sp?)) │ │ thatthey contain duplicate values. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3953 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/24/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 57197 S3/2.1 Support │ │ 23-Feb-94 20:24:30 │ │ Sb: #57096-2 Tables on 1 Screen ? │ │ Fm: David Silver 74145,1546 │ │ To: Debby Herman 72662,475 │ │ There is a file on this bbs called clrlst.zip. This file │ │ demonstrates the ability to have conditional colors in a │ │ list box. However the example is pure hand code and not │ │ verywell documented. In any event I attempted to apply the │ │ technique to a module created by the app generator using │ │ thebrowse template however each time the code passes │ │ through the borwse procedure, the color reverts back to │ │ normal. I traced through the browse procedure and found │ │ this was occuring at the accept statement. The browse │ │ procedure is very poorly commented and thus will be │ │ difficult to modify. My question was , perhaps your new │ │ template developer could point me in the right direction to │ │ change the browse template to accept conditional │ │ colors for the list box. David SIlver md │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3954 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 2/24/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using the Pen DOS Application Plaunch.Exe choosing the │ │ button DIR which executes a RUN in Plaunch14.Cla. Shelling │ │ out to DOS will not come out of GUI and the directory │ │ listing is not readable. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3955 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/24/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Pulldown Menus on a PEn Machine do not function. After │ │ some time I can get them to finally drop the menu but it │ │ will not execute anything. Gui functions different than │ │ text. │ │ R&D: Pen pulldown menus MUST BE ON LINE 1. There was │ │ another problem with this program that is now fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3956 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/24/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After Exiting a PEN Application the computer will not │ │ switch over to text mode. 'Mode bw80' must be executed for │ │ text mode operation. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3957 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/24/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Text mode Pulldown menu is unreadable, system hangs when │ │ .exe loads. │ │ R&D: Fixed for next make after 3:00pm, 2/25/94. Please test │ │ ASAP. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3958 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/24/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ OPENING A TEXT MODE SCREEN HANGS THE SYSTEM │ │ MD: This should be fixed...however I could not test the │ │ provided program because JUSTSC01.CLA was not included. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3959 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 2/25/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John P. McCarron 71773,3360 MSG#:56961 │ │ Did you know that under 3007, the Delete Empty Modules will │ │ delete the RGB modules added for VGA Colors? This is not a │ │ biggie, but these modules were NOT empty and were being │ │ used AND I had to add them back. │ │ FYI, │ │ John │ │ R&D: Yes, external modules which had no prototyped │ │ procedures but specified an include file were incorrectly │ │ viewed as empty during the delete operation. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3960 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 2/25/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick Weiss 71764,1312 MSG#:57031 │ │ I have encountered the the following problem a couple of │ │ times while trying to copy a BROWSE procedure. │ │ First, I highlight the proc, and enter CTRL-C and give │ │ it a new name. Then I change something, usually the access │ │ key and limit fields. │ │ If the original procedure had 2 fixed lines in the │ │ table, the new proc is garbled on the first 2 lines. The │ │ second line appears on the first and a couple of lines of │ │ data appear on the next couple of lines. I have tried │ │ setting fixed lines to 0...this works fine except I want │ │ those 2 fixed lines. If I then change from 0 to 2, the same │ │ problem recurrs. I have even tried deleting the scrolling │ │ fields and re-entering to no avail ( but if it did work it │ │ would be similar to creating a new proc anyway). │ │ R&D: So far, I am unable to reproduce this scenario. If │ │ anyone has an app that does reproduce it, please send it to │ │ me. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3961 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/25/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Scrolling a PEN list box is not moving passed the number of │ │ records on the screen. If the list can display 18 records │ │ and you add 25, the user cannot see 19 through 25. │ │ R&D: Fixed for next make after 3:45pm, 2/25/94. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3962 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 2/25/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Documentation for CIRCLE, RECTANGLE FILL parameter is │ │ confusing. It does not state clearly that the fill │ │ parameter is is a YES or NO option. By reading the │ │ description is sounds like I can draw a circle w/ a line │ │ color such as Red and fill it w/ LightBlue. │ │ Maybe it should read something like: When Fill is nonzero │ │ the figured will be filled w/ the color specified in the │ │ COLOR parameter. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3963 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 2/25/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Arthur Svensson 71554,3162 MSG#:57137 │ │ The movement of text seems inconsistent. In 'good ole' 2.1 │ │ pressing ^M hi-lited the text to be moved. After pressing │ │ ENTER the hi-lited text moved and 'displaced' the │ │ unselected text. In true WYSIWYG fashion you could see │ │ where the text would be placed before you pressed the final │ │ ENTER key. │ │ In 3.0 the 'displacement' doesn't occur ... the │ │ elegant WSIWIG if 2.1 is gone. If moving text 'down', │ │ the selected block is moved one line _below_ the visual │ │ 'release' point (As I recall the same happens when moving │ │ text 'up'). This causes my feeble mind to churn & churn. │ │ It's not a big deal _but_ it would make life easier │ │ for those of us who use both 2.1 & 3.0 to have a │ │ consistent Editor interface. │ │ Please mention it to the IDE │ │ designers. TIA. │ │ ----------------------------------------------------------- │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3964 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If I hold the pen button down and double tap on an entry on │ │ a listbox, the screen that appears seems to osmotically │ │ take on characteristics of the screen it is overwriting. │ │ It is really realy weird. │ │ MD: I'm going to need some demo of this one. │ │ QA: Done. Let's get it fixed. It appears to happen on the │ │ 2nd set of double taps WHILE the button is held. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3965 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using the PLAUNCH App, if I select the option to set System │ │ Date or System Time AND i do not have a Keyboard attached. │ │ I'm SOL! I cannot pop up an entry fiel;d or keyboard w/ │ │ the Pen to change the date or time. │ │ MD: I'm not sure that _I_ can do anything about this...when │ │ you run something from a Clarion Pen program, control is │ │ retained by PenDOS, _not_ me. │ │ MD II: This should work OK now, I found a workaround. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3966 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 2/25/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Database Browser │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Bob Pompei 74132,1002 MSG#:57210 │ │ I was experiencing probelms reading a Paradox 3.5 .DB file │ │ with a CDD 3007.1 application so I decided to do some │ │ testing. I created a Paradox 3.5 .DB file with 10 alpha │ │ fields (each being 30 chars) and the first one designated │ │ as a key field. When I start CDD (3007.1) and try │ │ to read the Paradox database I Xtrace after I pick the │ │ Order. If I shorten the PDOX record length to 260 bytes or │ │ less CDD reads it ok. If I delete the key fields from PDOX │ │ and .DCT it also reads into CDD. Has anybody │ │ experienced a similar problem? │ │ From Greg_W: I not sure if this is a driver bug or Browser │ │ bug or user error. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3967 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Nick Van Eldijk 71613,544 MSG#:57286 │ │ In the code generated with the help of the ScreenTemplate │ │ just before opening the Screen and in the Prodedure Return │ │ Routine a CheckOpen is done. I tried to avoid this by not │ │ putting any file in the 'primary', but put seven files in │ │ the 'other data'. One of them is -for no reason it seems- │ │ used in the CheckOpen(file). This is a situation where I │ │ don't want this because the path and filename will be │ │ defined in that same Screen, thus there is no valid │ │ path/filename when the first CheckOpen() executes; which │ │ will cause a Halt of course. Putting a '!' in front of │ │ #insert(%FileControl) in the Template file helps. │ │ Nick │ │ R&D: (Tom Moseley) This problem is due to Generator │ │ generating code for the first file in "Other Data" as │ │ Primary if no Primary is defined. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3968 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user -=- message attribute on a radio button │ │ individual items when the radio button is the first field │ │ on the screen causes a strange occurance when cancelling │ │ off of this screen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3969 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/25/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ decimal Pictures are displaying incorrectly, i.e. │ │ @n$13.2 displays (two) decimal points, multiple commas and │ │ the $ sign is displayed as the first entry char. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3970 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 2/25/94 │ │ Reported In : 3007 RevisedDate : 3/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007.1 - when using an @D3 picture either in a browse or │ │ form, on the screen it shows a Month with only 2 │ │ characters, even though it should have 3 characters for the │ │ month-but when the app is run, it does show 3 characters. │ │ R&D: Fixed in screen formatters; fix still needed in │ │ report formatter. It is fixed in Report formatter also! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3971 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Type inconsistency Overlay, Overlay DLL and Static model │ │ _Pen$setup_window. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3972 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After compiling testpen.cla in OVERLAY, OVERLAY DLL, and │ │ the STATIC model a warning is generated during link time. │ │ Graphic Row is duplicated during link time. The warning │ │ will only appear if the program does a compile and link. │ │ Linking the program will not cause the error. │ │ Q & A: The Graphic Row error will be documented. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3973 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Text mode: after completing a field with an @n3 picture │ │ and entering data in any other field the @n3 field │ │ displays a block character before each number in the field. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3974 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Text mode: buttons are displaying the & for the hot char. │ │ MD: Fixed...next make after 11:00am,3/1/94 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3975 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Text mode: List boxes cannot be scrolled │ │ MD: An example is needed, please. List boxes scoll just │ │ fine on my test programs. │ │ MD II: This should work OK now. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3976 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Text mode: enter and exit a few procedures (4 or │ │ 5 times) eventually system hangs. │ │ MD: I believe I found this one. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3977 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 2/28/94 │ │ Reported In : 3007 RevisedDate : 3/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you try to delete a tagged "read only" file with other │ │ files tagged, you will get a warning "1 File(s) Still │ │ Tagged (couldn't fit)" Shouldn't "couldn't fit" be changed │ │ to "Read Only"??? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3978 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 2/28/94 │ │ Reported In : 3007 RevisedDate : 3/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you tag all files in a directory, they delete them, the │ │ highlight bar will return over the "DOS Command" entry │ │ field, or it will not show up at all. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3980 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 2/28/94 │ │ Reported In : 3007 RevisedDate : 3/04/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user -=- btrieve tsr bug -- set( key key │ │ )previous is reading the wrong record -- when having a │ │ three part key.. providing the first two componets with │ │ the correct value and clearing the third to the highest │ │ value using clear.. then issuing a previous /\ note this │ │ kind of looks like automumbering code. this apparently │ │ happens only with the tsr... with the nlm or using the │ │ clarion driver seems to work. │ │ R&D: Cannot reproduce the problem. My test code is in zip │ │ file │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3981 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Text mode: Virtual screen; cannot scroll screen. │ │ MD: Next make after 11:00am,3/1/94 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3985 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30071 RevisedDate : 2/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Start CDD w/ a command line parameter for a DCT that does │ │ not exist. This will take you into a new DCT., skip the │ │ Description and then Press ESC once the File Properties is │ │ displayed. Now press AltF C to close the .DCT. Select NO │ │ to save changes. On some machines you will get the │ │ Hardware Problem Mgmt Window, on others it will save to the │ │ DCT anyway. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3983 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 2/28/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ NAME(file) does not return the correct result if the file │ │ was opened using a relative path. │ │ Test program: OPEN in test suite │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3984 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ On page 2 of the Pen Library Reference manual Pen Gesture │ │ α and ^ with a pen tap to paste is not copying a field, │ │ nothing happens. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3986 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 2/28/94 │ │ Reported In : RevisedDate : 2/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ SKIP(file,1);SKIP(file,1) only skips one record instead of │ │ two. │ │ Test program: SKIP │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3987 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Field() and selected() are not returning the same value as │ │ stated in the docs. │ │ MD: It would help if, while in the loop that is supposed to │ │ be checking FIELD() and SELECTED(), you put something in │ │ there to display FIELD() and SELECTED(). Nothing is being │ │ changed in the fieldequals and selectedequals fields. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3988 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Horizontal Scroll is not working at all, GUI and text mode. │ │ MD: Should be fixed now. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3989 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 2/28/94 │ │ Reported In : 3007? RevisedDate : 2/28/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Mike, │ │ When using the up-carat gesture on a pen field, it would be │ │ nice to have the field's prompt displayed so the operator │ │ knows what needs to be entered. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3990 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 2/28/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RUN() re-enters PENDOS and corrupts the system, reboot is │ │ only viable response, else you will suffer bizarre results. │ │ MD: There was a problem with the library, BUT. Doing a │ │ RUN('C:\DOS\COMMAND.COM DIR /P') is doing something that │ │ you wouldn't expect it to (it happens in a non-pen clarion │ │ program as well as from the DOS prompt also). The '/P' is │ │ not being used as a parameter to DIR, but as a parameter to │ │ COMMAND.COM which tells COMMAND.COM that this will be the │ │ _primary_ COMMAND.COM, thus "restarting" the system. Add a │ │ '/C' after COMMAND.COM and things will work. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3991 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 4/01/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Browse/Form problems involving "Error: Attempting to │ │ Change"and "Record Not Available" │ │ Example File included. │ │ R&D: Example file not available. A problem fitting into │ │ the above description could be any number of things, │ │ driver, template, language... An example file is needed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3992 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul M. Blais 72103,111 MSG#:56535 │ │ After some more testing I found the problem is not any │ │ limit on MSG, but rather yet another bug with CHANGE(). │ │ After the screen opens I run some change commands to reset │ │ all the screen values. As soon as I attempt to issue a │ │ CHANGE() command on a check box that has a message, the │ │ hangoccurs. It does not occur if there is no message. This │ │ is aproblem with all memory models and with and without GUI. │ │ Hope this focuses the efforts to get this fixed. -Paul │ │ MSG('Thanks') │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3993 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Leschak (CompuSyste 71461,471 MSG#:56502 │ │ i would like to know if there is some way that i can │ │ process all fields in a record and get a record layout at │ │ runtime. │ │ i was thinking this might be done via some SEND │ │ commands, possible something like this: │ │ !*** get the number of fields in a file │ │ lFields# = SEND('FILE=MYFILE.DAT,FIELDCOUNT) │ │ for i#=1 to lFields# │ │ !*** get the name of the i#'th field │ │ sFldName" = │ │ SEND('FILE=MYFILE,GETFIELDNAME,i#) │ │ !*** search │ │ for a record lErr# = │ │ SEND('FILE=MYFILE,KEY=MYKEY,'&sFldName&"'='jones') │ │ !*** │ │ get the field value │ │ sFldValue = SEND('FILE=MYFILE,GETFIELD='&sFldName") next i# │ │ then i │ │ could do some limited (or unlimited) user defined functions │ │ and queries with this capability. boy, the things we could │ │ do with this kind of functionality would be incredible! │ │ jsl │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3995 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/01/94 │ │ Reported In : 72 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ International money pictures are displaying the fixed │ │ characters in places meant for entry. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3996 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/01/94 │ │ Reported In : 72 RevisedDate : 3/02/94 │ │ Fixed In : 72 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Entry fields with the INS attrib display a block over the │ │ character when it is being penned, a redisplay gets rid of │ │ the block. │ │ MD: This should work OK now. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3997 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Kurt Gengenbach 73707,1044 MSG#:57331 │ │ Simple browse, no range or filter. Let's take a typical │ │ code/description browse, sorted by code number. Our field │ │ wants to lookup that code. If code numbers range from 1 to │ │ 5 in that table, and we type 9 for example, when the browse │ │ is called (because 9 is an invalid entry), it doesn't list │ │ any records and highlights insert. One small note, the │ │ browse has a non-incremental locator on code number. │ │ Kurt │ │ From Greg_W: I duplicated this problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3998 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Is there a switch to cause screen formatter to use │ │ "pressure sensitive" │ │ scrolling during virtual screen designs? On my system, the │ │ normal auto-scroll │ │ feature makes the screen move so quickly I cannot control │ │ it very well. (If │ │ not, move this under suggestions). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 3999 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Bruce Goldman 74045,444 MSG#:56616 │ │ I noticed that the 'display' statement at the end of the │ │ SecondaryLookups routine has been removed. It seems to be │ │ creating a problem. │ │ I have a form with several lookup fields that display a │ │ related field from the lookup file. I also use the │ │ technique from the Advance.app to display two different │ │ fields from this same lookup file (by aliasing the file │ │ names) │ │ HOWEVER, now that the 'display' │ │ statement is gone from SecondaryLookups it wasn't │ │ displaying correctly. │ │ I have even │ │ recompiled the advance.app with the 3007.1004 templates and │ │ it doesn't work the same as the .exe included with │ │ advance.app. │ │ Along with this problem is the following: when doing a │ │ lookup with a hot key, when it returns and cycles through │ │ the form the SecondaryLookups routine is NOT triggered │ │ because the two related values ARE set equal in the code. │ │ Therefore the related fields wont display correctly │ │ either. │ │ When I added a display statement at the │ │ end of the secondarylookups routine, and a display │ │ statement in the 'when selected ' code of the lookup fields │ │ then all displayed as expected. │ │ Hope you can get this │ │ straight. Again just recompile the advance.app demo and │ │ see what happens when you cycle through those different │ │ state fields when updating addresses. │ │ R&D: The problem described has been fixed in 3007.2 │ │ templates (3007.105). However, instead if putting the │ │ DISPLAY in SecondaryLookups ROUTINE (which I won't do │ │ because initial call is before screen opening), the DISPLAY │ │ takes place in main-line code after the DO SecondaryLookups │ │ call. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4000 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:56260 │ │ The (Select ?LIST) BUG in the Browse template that was │ │ 'fixed' in 3007.103 is still there. │ │ Make & Run \CLARION3\EXAMPLE\ORDERS.APP. There is a │ │ menu called Update Files. Add a new customer & add a new │ │ product. │ │ When you add the new customer, on returning to │ │ the browse from the form, the ?LIST is not updated. When │ │ you add a new product, the browse updates correctly. │ │ From Greg_W: I duplicated this. │ │ R&D: (Tom Moseley) The Clarion File Driver is clearing │ │ POSITION after a COMMIT. This does not happen with │ │ other file drivers, should not happen, and did not happen │ │ before 3007 (as far as I can tell). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4001 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/01/94 │ │ Reported In : 30072 RevisedDate : 3/02/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using PenGUI program, a text field seems to be causing the │ │ computer to hang. The formula was used to create the text │ │ field. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4002 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Question │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Harrison A. Curtis 72730,1402 MSG#:57801 │ │ By increasing the size of the stack to accomodate the │ │ arrays the problem is solved. I would suggest the error I │ │ was getting would indicate a stack overflow instead of a │ │ memory allocation error. │ │ This brings up some interresting questions. In │ │ protected mode, what is the limit of the stack? Can the │ │ stack exceed the 64K limit? Is the 64K limit for an array │ │ still enforced in protected mode? Is there a way to assign │ │ certain memory allocations to be static in a │ │ procedure? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4003 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/01/94 │ │ Reported In : 30072 RevisedDate : 3/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ After exiting the PENGUI APP you are now in text mode, most │ │ excellent. However, the mouse cursor remains on and NOT │ │ active when running CDD the mouse is now inactive. │ │ MD: This is strange because I can't get it to happen. │ │ However, I did add something to the exit routine that could │ │ solve this problem, so let me know if it is still broke. │ │ QA: Mouse Cursor is still appearing │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4004 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/01/94 │ │ Reported In : 72 RevisedDate : 3/02/94 │ │ Fixed In : 72 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Key-in pictures: can't enter data, and after exiting the │ │ OVR window, the display shows a hi-lite block around the │ │ field. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4005 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DP DateReported : 3/01/94 │ │ Reported In : 30072 RevisedDate : 3/03/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Scrolling is not functioning with the VIEW template. │ │ MD: I think this was the one where your pen wasn't │ │ calibrated so you weren't hitting the buttons cuz it works │ │ fine on my machine. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4006 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/01/94 │ │ Reported In : 30072 RevisedDate : 3/03/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Print to a file using testpen.app, bring up the entry field │ │ to type in the file name, press OK. The screen is not │ │ restoring, however you can press the OK button and the file │ │ is written to disk. │ │ MD: This works OK with the latest stuff. The screen where │ │ you view the file needs to be redone for pen because the │ │ fields are going outside the window area. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4007 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Reference: Project 3019 │ │ .CLA was converted from 2.1 to 30071. Every time the │ │ screen formatter was invoked a Memory Protection Violation │ │ appeared and an XTRACE. │ │ R&D: Problem was with string constants in the screen │ │ structure being split using ampersands and continuation │ │ lines. Workaround is to combine any string constants into │ │ a single constant. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4008 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/01/94 │ │ Reported In : 30072 RevisedDate : 3/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ PenDOS COPY FIELD α ^, the period (tap) must be in the │ │ middle of the ^. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4009 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 3/01/94 │ │ Reported In : 3007 RevisedDate : 3/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : ReportWriter │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007 Report Writer -- user reports that using a │ │ multicomponent key, second group header repeats after each │ │ record in the body │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4010 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in a file with a memo field, you will get 'record not │ │ found' if you add(file) and then put(file). if a │ │ get(file) gets issued in between the add() and put() you │ │ will not get the error. │ │ this works fine with the clarion driver and the LRM states │ │ that put() will write to the location of the last record │ │ accessed with a NEXT, PREVIOUS, GET or ADD │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4011 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When issuing a RUN statement, apparently the PenDOS library │ │ is terminating the current session of PenDOS. │ │ Example: Use the PLaunch application. Make a menu option │ │ execute the TIME DOS command. When executing that program │ │ you cannot do _anything_ with the pen. If you have a │ │ keyboard active and complete TIME, you come back in to │ │ PLaunch with the Pen active. │ │ Running TIME from the prompt with the Pen active allows you │ │ to call up a keyboard or writing window to enter a value. │ │ Running TIME from a Clarion RUN() does not. │ │ MD: Tried and verified that it works correctly. I can pull │ │ up the writing window after running command.com /c time. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4012 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using PullDowns & GUI going to a screen w/ just a button on │ │ it, the screen is automatically completing. │ │ See test file, and pick any one of the Drawing Options. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4013 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/29/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Select Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard A Rasbach 71551,3154 MSG#:57596 │ │ I'm running 3007.100. I am using a the SELECT template to │ │ select a record from a Clarion File. Being a CPD user I │ │ happend to press CTRL-ENTER to change a record. When I did │ │ that, the update FORM was called, however any of my changes │ │ to the record were not saved. I found that the FORM │ │ did not set the Action variable when CTRL-ENTER is pressed. │ │ I think the FORM template should be changed to set the │ │ Action variable to UpdateRecord if CTRL-ENTER is the │ │ keycode that causes the FORM to be called. │ │ R&D: Select (or Lookup, Validate, Browse in Select mode) │ │ were not changing keycode() to EnterKey. Fixed in 3007.2 │ │ templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4014 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 MSG#:57656 │ │ I have a suggestion/request for 3008 or sooner. How │ │ about a chart (grid) with the available file drivers on │ │ one axis and the features on the other. This would show │ │ at a glance which drivers support which features. For │ │ example, │ │ Clarion BTrieve dBase III+ │ │ dBase IV Paradox │ │ ADD x x x │ │ x x POINTER x │ │ ? POSITION x x x │ │ x x │ │ You could also use a number instead of an x if │ │ there is a need for a special note for that │ │ feature/driver combination. This would sure make conversion │ │ between file formats a lot easier than it is now. │ │ Thanks, │ │ Joe Bouterse Creative Solutions, │ │ Inc. Indianapolis, IN │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4015 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Nick Van Eldijk 71613,544 MSG#:57685 │ │ The .pr file is not always updated right. I imported some │ │ procedures from another app made with SuperTemplates and │ │ the.pr file kept on naming some 'Super' libs. There was no │ │ callwhatsoever to any Supertemplate code. After deleting │ │ this from the .pr file everything was back to normal. │ │ This information probably got into the .pr file │ │ during import. Nick │ │ R&D: Yes, the project file system under Generator was │ │ unable to delete "non-#compile" entries placed in the .PR │ │ file (ie. #PROJECT('myentry.lib') or XXXX.LIB entry in │ │ Module View). This capability has been added in 3008. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4016 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : REPORT ENGINE │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Bob Divine 76130,3536 MSG#:57688 │ │ Boy, am I getting tired of reporting this one. As reported │ │ in 3002, 3003, 3004, 3005, 3006 & now 3007.104....reports │ │ still can't count. │ │ If you set any of the controllers for page breaking, │ │ (allow, last, etc) any lines in the next detail do not get │ │ counted to determine how many line there are to print if │ │ there is a suppress on a line. I have a report with a │ │ length of 58 with a Last on the footer. It will │ │ print 66 lines if I have 8 lines in the footer with the │ │ suppress attribute on them. It will print 65 line if I │ │ have 7 lines with suppress and so on. If I eliminate all │ │ suppress attributes, the report prints 58 lines. │ │ Without knowing how many child │ │ records there are, in advance, I can not control with any │ │ accuracy page breaks. I can put a counter in to count the │ │ child lines as they are printed, but I can only control │ │ pagelength at runtime. Either give me the ability to │ │ manipulate pagelength and allow dynamically, or FIX THE │ │ REPORT! Bob │ │ From Greg_W: I requested an example if he has one. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4017 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Marjolein Katsma 100276,2414 MSG#:57744 │ │ This may be a linker buguette: │ │ I was trying to create an "isolated example" to demonstrate │ │ another problem (still working on it - will upload when I'm │ │ really stuck) when I ran into this. │ │ Originally it had an arry of 31 elements; I deleted one, │ │ and left the LOOP statement reding LOOP i# = 1 to 31. The │ │ program was made with the following project file: │ │ #system auto exe │ │ #model overlay │ │ #pragma data(stack_size=>24576,threshold=>4096) │ │ #pragma optimize(cpu=>86) │ │ #pragma check(stack=>on,index=>on) │ │ #pragma link_option(map=>off,case=>on) │ │ #compile oksort.cla /define(GENERATED=>off) │ │ #pragma link(%clapfx%ascii.lib) │ │ #link oksort │ │ As you can see: no DLL's and trapping for index on. │ │ When the program ran, it returned to the DOS prompt with │ │ the following error message: │ │ : DLL load failed. Is your PATH set correctly? │ │ Note the colon at the start of the message: │ │ actually the END of a previous message in the EXE. The │ │ message I would have expected: "Array INDEX out of range" │ │ is nowhere to be found in the EXE. │ │ Looks like the linker not only put │ │ in the wrong error message but also messed up the pointer │ │ to the start of the message │ │ Apart from that, the program │ │ produces an _empty_ ERRORINF.$$$ (zero bytes), and │ │ sometimes it does not even get this far, but locks up my │ │ system completely (running under DesqView: quite a feat!) │ │ or just 'reboots' (closes) the window it's running │ │ in. I have not been able to figure out when these crashes │ │ occur rather than displaying the (wrong) error message. │ │ Obviously, │ │ not changing the loop condition was my fault, and because │ │ the program is so tiny I soon realised what was wrong - but │ │ at least I would have expected a message that told me so │ │ and not something completely different? │ │ Should be easy enough to reproduce (any program that does │ │ nothing else but loop through an array one time too many │ │ would do it) but if you need more info let me know. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4018 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ken J Horii 76340,1234 MSG#:57779 │ │ I have been working with CDD Version #3, Release .104. I │ │ used the files in .\EXAMPLE to derive this "HELP ME" text │ │ file │ │ MSG#: CD3-001.TXT │ │ RE: CDD3 Release 3007.104 │ │ ABSTRACT: CDD3.EXE does not like to do the │ │ following... . 1) execute hello.exe from │ │ redirected sub-directory H:\BIN . 2) does not │ │ appreciate empty sub-directories H:\DLL or H:\LIB . │ │ 3) does not redirect *.BAK or *.BPP to H:\MSC . │ │ 4) does not allow comments beginning with ! or ; │ │ DESCRIPTION of PROBLEMS: │ │ 1) I used the hello.prj and │ │ hello.clw to test my environment. I altered . the │ │ CLARION.RED for my development configuration. I want to │ │ keep . source files, binary files, and intermediate files │ │ in different places. . To this end, the batch file and │ │ redirection were changed to this... . │ │ . C3.BAT │ │ --- start CDD3 batch file (partial) . │ │ path h:\bin;h:\src;k:\cdd3;%path% . │ │ . │ │ CLARION.RED --- CDD3 IDE redirection file (partial) . │ │ *.PR = H:\SRC . │ │ *.CL = H:\SRC . │ │ *.OBJ = H:\MSC . │ │ *.EXE = H:\BIN . │ │ . │ │ The selection of Make and Run, does its job! Hello.obj is │ │ left in the . sub-directory H:\MSC. The binary executable │ │ file is written in H:\BIN. . The "SHIP LIST..." shows that │ │ I only need to ship "H:\SRC\HELLO.BIN". . . │ │ *BUT*, 'run' returns [ Project System Problem ] │ │ displaying, hello.EXE; . Error: program file Not │ │ Available. <====== ??? . │ │ . From the dos prompt L:\> hello runs │ │ as expected!!! │ │ 2) I created the following │ │ subdirectories in H: for CDD3... . │ │ . H:\BIN; H:\DLL; │ │ H:\LIB; H:\MSC; H:\SRC; . │ │ . Since HELLO.CLA does │ │ not need a hello.dll or hello.lib, the . subdirectories │ │ H:\DLL and H:\LIB should be *empty* ! . However, the │ │ (V)alidate of the D(i)rectory of the CLARION.RED returns . │ │ a [ Project System Problem ] "NO Files exist at H:\DLL\*.*. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4019 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I _finally_ figured out what's been locking up my computer │ │ 9 out of every 10 │ │ times after a Clarion 3.07.1.4 generated executable │ │ terminates (while running │ │ under Windows OR under DOS). │ │ The problem NEVER occurs (not even once during 250+ tests) │ │ if LOADSYMBOLS and │ │ LOADBORDERS is never called. I haven't confirmed which one │ │ is actually the │ │ cause (maybe both) since I always call them together, but │ │ there's little doubt. │ │ Just thought I'd let everyone else know how to avoid the │ │ same pitfall. You'll │ │ have to live without the pretty mouse pointer, but it's a │ │ very worthwhile │ │ trade. │ │ The problem must be related to my hardware/software │ │ configuration. And it is farily random, though │ │ it happens often. I was hoping someone else was having │ │ similar results to help narrow things down a bit. All I can │ │ tell you is that I noticed that the last │ │ gasp of a Clarion EXE appears to be resetting the PC's │ │ character set back to normal. It is this action _at that │ │ time_ which seems to lock up my computer when running under │ │ DOS, or cause a GPF when running under Windows. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4020 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mike Hanson, BoxSoft 73234,1447 MSG#:57785 │ │ There is an implication to your new CHANGE() command that │ │ needs to be fixed. Here is the problem: │ │ 1. You have a field with lookup verification. 2. The │ │ field's edit procedure has the following code: │ │ IF REFER() THEN DoSomething. │ │ 3. The lookup procedure executes the following code: │ │ CHANGE(?,NewVal); SELECT(?); PRESS(TabKey) │ │ The code in #2 is not processed properly if a lookup │ │ is performed. As first I was going to suggest that you │ │ always set REFER() after a CHANGE(), but it really applies │ │ only in this situation. │ │ Maybe we need a SETREFER() command to augment │ │ the system. Otherwise, we might need to circumvent the │ │ fancy new CHANGE() command with the following technique: │ │ ERASE(?); SELECT(?); │ │ PRESS(NewVal); PRESS(TabKey) │ │ Of course, this is why you │ │ added the CHANGE() procedure in the first place. Catch you │ │ later! │ │ -=> Mike Hanson, BoxSoft │ │ <=- │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4021 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Equate labels appear to be CASE sensitive. │ │ Example: If I change ?Insert to ?INSERT, the insert button │ │ no longer works. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4022 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Define a numeric field w/ a picture token of 11.2- │ │ 2. Place the field on a screen. │ │ 3. Make │ │ 4. Run on a PEN machine and try to enter a NEGATIVE Number. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4023 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using a Picture token of @K@@<<##__ZZK will not let me │ │ enter anything. ?s are returned for the Numbers and beeps │ │ when I try lower case letters where the _s are. │ │ See the LAST Page of the example form. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4024 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/02/94 │ │ Reported In : 3007 RevisedDate : 3/03/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ this was a problem in 3007.1-=- chkbook app is a good │ │ example-- as I type this memo I do not have the problem │ │ -- maybe this program is running a different release -- how │ │ do you delete a line in the memo for example if there is a │ │ blank line due to pressing the enter key, then a line of │ │ text how would you go about removing it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4025 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/02/94 │ │ Reported In : 3007 RevisedDate : 3/03/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Cshell only from the IDE: the DOS command line does not │ │ work. It simply takes me to the files listbox. A user │ │ said this does not always happen, however when I tried it │ │ it happened to me. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4026 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using GUI and clarion 3.0071. Application (protected mode) │ │ is using idle │ │ procedure to time stamp records for record locking │ │ purposes. I discovered that │ │ when a window is moved by the user the idle procedure stops │ │ being called. The │ │ idle procedure will not restart until the procedure is │ │ rearmed with idle(...). │ │ If the user never moves the window only works the buttons │ │ or the list box │ │ everythings ok. │ │ This application was almost out the door so this problem is │ │ kinda critical │ │ (because it affects the multiuser cap. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4027 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/03/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When a record is selected from a BROWSE for modifing, the │ │ first field on the form is blank when the update │ │ procedure(form) is called on a non-CUA screen. When │ │ something is typed in the blank field and then you try to │ │ save the record, you will get an 'ERROR 33 - Record not │ │ availible'. │ │ R&D: (Tom Moseley) - Mike, this is related to Bug #4048. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4028 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/03/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user - problem with collating sequences. │ │ ex. set ascii 154 before ascii 98. Now create a file with │ │ one field (a long) and add 1000 record. When you browse │ │ the file these records should be in the wrong order. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4029 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/03/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ See the Testfile. It appears that using Overprint next │ │ will end up removeing the first blank line in the report │ │ formatter. There are detailed instructions in the test │ │ file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4030 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/03/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The example for the NOTIFY group is missing a LONG field │ │ inbetween CritType and CritMsg. When you run the example │ │ from the manual, the error screen in ErrorProc shows some │ │ garbage in ErrDesc because of the missing definition. │ │ What is this exta field used for? │ │ Also, in the ErrorProc procedure I beleive the │ │ Opt=UPPER(KEYCODE()) should read as │ │ Opt=UPPER(CHR(KEYCODE())) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4031 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/03/94 │ │ Reported In : 30072 RevisedDate : 3/03/94 │ │ Fixed In : 30072 Status : Tested/OK │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ PEN$HIDE_CURSOR type inconsistency in every model. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4032 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/03/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ there is a problem in the 3007.105 templates on a form. │ │ autoincadd does not get defined in a form procedure when │ │ you are not using 'Return to caller' and no │ │ autoincrementing keys are defined. │ │ R&D: Fixed in 3007.2 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4033 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/03/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Load CDD Select Clarion. Select any of the options that │ │ will bring up the task list. Place the mouse cursor on the │ │ vertical slider and press the left mouse button. When │ │ holding the mouse cursor down, slide the mouse cursor down │ │ the vertical slider to the down arrow and watch the task │ │ list disappear. Release the mouse button and select Load │ │ or Remove an Xtrace appears. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4034 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/03/94 │ │ Reported In : 3007 RevisedDate : 3/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports -=- a report with no body that has a lookup in │ │ the footer is getting the wrong record -- │ │ R&D: Does not appear to be failing in 3007.2. Code │ │ generated confirms with what you'd expect of a Many:1 │ │ lookup in the Page Footer code. With the fixes betweed │ │ 3007 and 3007.2, it's possible this problem was fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4035 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/03/94 │ │ Reported In : 30071 RevisedDate : 3/03/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ cannot use numbers as a hot "letter" on a pulldown menu. │ │ cannot use special characters Ä, Å, or Ö as a hot letter on │ │ a button. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4036 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/03/94 │ │ Reported In : 3007 RevisedDate : 3/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ go into the file menu and choose change directory. tab over │ │ and choose a directory. now hit escape or alt-c or tab to │ │ the cancel button. when you cancel your directory still │ │ gets changed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4037 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/03/94 │ │ Reported In : 30072 RevisedDate : 3/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Execute RunText.Exe Select the first button. When you │ │ return to the menu the buttons are not fully restored until │ │ you press one of the buttons again. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4038 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/04/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When the cursor is placed on a memo field at the first │ │ column of the existing first line and you press <enter> in │ │ insert mode, it will not move the current line down... in │ │ other words, there is no way to insert a line before the │ │ first line of a memo field unless you press the space bar │ │ to move the line down -- reported by Proj 2878 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4039 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/04/94 │ │ Reported In : 30071 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The select template is missing the code regarding │ │ if keycode() = shiftEnter │ │ calledaslookup = true │ │ . │ │ called as lookup is always true so what happens is that the │ │ code for of ?list. │ │ if keycode() = enterkey │ │ do procedure return. │ │ if the user puts a call to a procedure on the "when field │ │ is completed" it doesn't execute. See the order example, │ │ print single report. │ │ R&D: Fixed with 3009 browse keycode handling rewrite │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4040 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/04/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ On a virtual Text Screen when I scroll a button off the the │ │ left I get a wierd "shadow" or remnant of the Button │ │ remaining behind. │ │ From the Screen Function Pulldown select "Virtual Screen" │ │ Scroll to the Bottom and then scroll to the right. keep an │ │ eye on those buttons as they move off the left side. │ │ This is livable and we won't hold up the masters. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4041 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 3/04/94 │ │ Reported In : 3007 RevisedDate : 3/25/94 │ │ Fixed In : 3008 Status : Tested/OK │ │ │ │ Section : ASCII Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If copy or rename fails there is memory leakage equal to │ │ the size of the name of the file │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4043 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/04/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when importing a 2.1 table which has a locator field │ │ underneath the scrolling area, the screen varible does not │ │ get created in local data and the screen field does not get │ │ put inside the listbox. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4044 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/04/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I realize this is somewhat academic, since it is not │ │ supposed to work (though │ │ not documented), But issuing a SETGRAPHIC(90) in a GUI app │ │ that has PCX icons │ │ causes a text mode black icon to appear on top of the │ │ properly displayed and │ │ enabled PCX icon. So in addition to not supporting │ │ SETGRAPHIC(90), GUI does not │ │ like it to be there either. I guess this would qualify as │ │ a bug in a │ │ non-feature<g>. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4045 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/04/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ KeyCodes 3117 - 3127 are not working. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4047 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 58502 S8/3.0 Support │ │ 03-Mar-94 16:17:39 │ │ Sb: DimRadio & GUI │ │ Fm: Paul M. Blais 72103,111 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ Under GUI version 3007.1 the Clarion Internal DimRadio │ │ procedure does disable the radio button, but fails to │ │ display the button with a DIM attribute. The DimRadio │ │ procedure does appear to work properly in text mode or in │ │ GUI mode with CLAGRAPH=ALLTEXT. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4048 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When processing a non-CUA screen, the "Hot Key" attribute │ │ to buttons is not working. h:\bugrpt\files\4048.cla shows │ │ the problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4049 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Hardware Specific │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ all the libs and .dll files for browse.cla have been │ │ optimized for 286 therefore application will not run on XT │ │ machines unless browse.cla has been relinked by the user. │ │ Workaround. │ │ Bring up browse.cla in the editor. Change the project │ │ hardware settings from 286 to 8086/8088 and make the │ │ project for all memory models. If you get error window │ │ regarding "no exports" just continue, it will link okay. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4050 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 58516 S8/3.0 Support │ │ 03-Mar-94 18:02:51 │ │ Sb: ScrnFlds.Tpx Made Clear │ │ Fm: Douglas Johnson 75310,2035 │ │ To: Debby Herman 72662,475 │ │ For Tom Moseley: │ │ A small point, but perhaps a help in maintenance - │ │ GROUP %PrimeLookup in ScrnFlds.Tpx contains the following: │ │ #ELSIF(%LocateField) │ │ #FOR(%File) << │ │ #FIX(%Field,%LocateField) << │ │ #IF(%Field) << │ │ #SET(%LookupFromFile,%File) << │ │ ... check a bunch of stuff ... │ │ #BREAK │ │ #ENDIF │ │ It seems to me that the same thing could more easily be │ │ accomplished │ │ by getting rid of the FOR Loop and simply having: │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4051 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Gary Johnson 70154,2436 MSG#:58690 │ │ >> does by the way) In the source embed in the Source │ │ template, you are >> creating the screen for the first │ │ time, using the screen formatter, and >> the screen │ │ formatter defaults to full. There is no way to change │ │ this. │ │ This is what happened. Might I suggest that this is a poor │ │ default! When you say that there is no way to change this, │ │ I know that you must refer to us poor users out here. To │ │ you that do have the power to affect defaults, I would │ │ like to offer this as a suggested improvement to CDD. │ │ Gary Magness Vertical │ │ Systems, Inc Overland Park, KS │ │ From Greg_W: │ │ The suggestion is: When creating a screen for the first │ │ time default to a Window 25x80 rather than a FULL screen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4052 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:58750 │ │ If one takes the #PROTOTYPE('') out of the templates, then │ │ the programmer has control over it. It looks just like │ │ another #PROMPT and I'd like to be able to use it in │ │ exactlythe same way - that is, have the contents in a │ │ %Prototype symbol just like %Primary, %PrimaryKey, │ │ %Procedure etc. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4053 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RECEIVED EXPECTED END ERROR FOR THE FOLLOWING. IF PERIOD IS │ │ ON THE FOLLOWING LINE, NO ERROR IS PRODUCED. │ │ PROGRAM │ │ MAP │ │ INCLUDE('CLA_LIB.INC'). │ │ CODE │ │ SHOW(5,10,'THIS IS A TEST') │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4054 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/07/94 │ │ Reported In : 3007 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports -- shade function does shade on the screen but │ │ when printing using vpon to a postscript. And while issuing │ │ a boxfill if you hit a keystroke the keyboard function is │ │ not aware of it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4055 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 58846 S17/Priority Support │ │ 05-Mar-94 13:25:02 │ │ Sb: Word Wrap │ │ Fm: Scott Merritt 71140,2502 │ │ To: SYSOP (X) │ │ When are you going to finally fix the text field, object, │ │ whatever you want to │ │ call it. You know the problem. The routine inserts │ │ additional spaces into the │ │ wrapped string so that the only way it looks right is when │ │ the display area is │ │ the same dimension as the original text dimension. I can't │ │ believe it still │ │ works like this particulary when CDD is now capable of │ │ sharing a variety of │ │ data with other applications, DBMSs' and report generators. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4056 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/07/94 │ │ Reported In : 3006 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user -- chain on 3006 -=- when you chain to a │ │ new exe; files are being left open and its dll that go with │ │ it as well as its swapfile. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4057 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Use the supplied CLAs and Clarion file to view the records │ │ via the Dynamic Index. Either the BUILD() is hosed or │ │ Dynamic Indices are hosed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4058 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/07/94 │ │ Reported In : 3007 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports -=-=- 3007.1 -- form procedure NON CUA when │ │ uparrowing to the previous field the when field is selected │ │ code does not happen ... this was tested by the user as the │ │ first field │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4059 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ : 57181 S8/3.0 Support │ │ 23-Feb-94 18:43:49 │ │ b: Btrieve KEY Problem │ │ m: Francis Bussiere 70541,1153 │ │ o: Debby Herman 72662,475 │ │ debby, │ │ i am uploading BUG01.APP to demonstrate a problem with KEY │ │ segments that are part of a group and OVERlayed by another │ │ field. In File1 a single group is sed and it works; in │ │ File2 two segments from two different groups are used and │ │ the Btrieve driver fails to create the file properly │ │ (ERROR:29). The file is created without any keys. With an │ │ existing Great Plains file the Btrieve driver ails when │ │ accessing the file (ERROR:21). The problem stems from the │ │ fact that reat Plains creates the file without using the │ │ LString data type and I am │ │ trying to avoid having to set the length with hand code - │ │ see file 4059.zip │ │ Tech support project #3182 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4061 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ File shows bug in btrieve driver with the records key │ │ function. │ │ R&D: Just a note. The solution to problem is non-trivial, │ │ so due to other more important bugs may not be fixed for a │ │ while. The work around is to write a simple replacement │ │ code that searches for all records with NULL values and │ │ subtracts this from the RECORDS(file) value. (This │ │ is probably what the driver will have to do) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4062 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in 2.1 deformat works differently in the enclosed example. │ │ 3.0 does not return the negative number. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4063 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the following text field in a screen structure will cause │ │ anxtrace durring compile. see full example file 4063.zip │ │ test file,driver('basic'),pre(txt) │ │ tstrec record │ │ . │ │ . │ │ . │ │ . . │ │ screen screen(16,80) │ │ . │ │ . │ │ . │ │ row(13,3) text(2,76), use(txt:txtrec).... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4064 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/08/94 │ │ Reported In : 3007 RevisedDate : 3/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Xtrace when changing the name of a field that is being used │ │ in keys. In the example provided change the league │ │ filename to players. Now change the field name from pos to │ │ position and save the dictionary. This causes an xtrace on │ │ my machine. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4065 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 3/08/94 │ │ Reported In : 3007 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A Hot Field displaying a REAL from a file will not change │ │ value when scrolling between a value of 4.5 and 8.0 or │ │ other sets of consecutive numbers with a difference of 3.5 │ │ where the low value is > 4.5. Test File: 4065.ZIP │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4066 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/08/94 │ │ Reported In : 3007 RevisedDate : 3/09/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reported -=- real section template tokens -=- │ │ When using #set to give a userdefined symbol a value; and │ │ this is done above the map and modules in the template. │ │ This value cannot be retrieved in any other tpx file. │ │ R&D: "Global template symbols" can ONLY be #SET in the │ │ #PROGRAM template. Everywhere else symbols which are #SET │ │ are created and destroyed at the local #PROCEDURE scope. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4067 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/08/94 │ │ Reported In : 3007 RevisedDate : 3/08/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ USER WOULD LIKE TO HAVe the help id's for a screen be │ │ defaulted to the procedure label. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4069 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : REPORT ENGINE │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Kerwin 74017,27 MSG#:58877 │ │ I have the 3007.105 template patch. When I put the Last │ │ attribute on a Report Group, it advances the page number. │ │ Interestingly, the first time I run the report, the pages │ │ are numbered 1, 3, 5, ...etc. The second and subsequent │ │ times the pages are number 2, 4, 6...etc. │ │ FYI, Kerwin │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4070 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Gene Lawin 76437,2117 MSG#:58891 │ │ I'm using the same environment as you (GUI, extender, and │ │ 3007.1) and I noticed that when I open a window and the │ │ user goes to move that window (clicks on the title bar and │ │ gets white 'border' image) any armed IDLE procedure becomes │ │ inactive. Simply arm an IDLE procedure to do something │ │ periodically, open another window and click on the title bar │ │ and move the window. Does the IDLE procedure stop? If so │ │ this is a pretty interesting bug. │ │ From Greg_W: 2 other users confirmed that this happens. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4073 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ According to the docs pg 7-10 the following code should │ │ compile. I can't get it to. │ │ program │ │ pic string(@n7.2) │ │ field1 string(10) │ │ code │ │ field1 = '1234567' │ │ show(1,1,field1,pic) │ │ ask │ │ Compile error "Parameter must be picture" │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4074 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How can I get insert mode to become the default for the │ │ text editor,app │ │ generator and to remain in effect? I'm screaming sick and │ │ tired of the various │ │ IDE tools flipping insert mode off when I have it enabled │ │ (by pressing the INS │ │ key). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4075 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ From Greg_W: After explaining why the Browse doesn't │ │ support a vertical scroll bar I recieved the following │ │ "suggestion". │ │ Greg, I've seen this explanation offered at least twice │ │ before by you guys. The problem is, our clients are going to │ │ complain to us and we'll complain to you until this is │ │ madeto work differently, no matter WHAT the explanation is. │ │ Whenever there's a table of records displayed and the │ │ operator knows *(*&% well there are more records above │ │ and below the display, if he has a vertical scroll bar │ │ ANYWHERE in the application, he is going to expect one │ │ EVERYWHERE in that situation, and will expect to be able to │ │ drag it up or down to scroll the data. Period. Especially │ │ if he's a client who doesn't know beans nor care about │ │ queues, listboxes, or whatever. │ │ If it's a basic, core system characteristic │ │ that's is a super big deal to fix, it's still a problem. │ │ It seems to me something is going to have │ │ to be done about performance of queues and list boxes, │ │ anyway. The current convention of loading the queue │ │ with a list-box-worth of records is causing │ │ horrible performance problems when one more record is │ │ scrolled into the list box (up or down). I don't know what │ │ you guys are doing differently from the rest of the │ │ industry -- a scrolling data table with quick, │ │ responsive movement up and down the table seems to be sort │ │ of a basic capability one has come to expect. CDD can't do │ │ that yet. It's going to have to, somehow. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4076 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/09/94 │ │ Reported In : 3007 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Select Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Code that is placed into the "When Field is Selected" embed │ │ of the "Select" button will never get executed unless you │ │ place "CalledAsLookup=1" in the setup proc. of the Select. │ │ R&D: Fixed with 3009 browse keycode handling rewrite │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4078 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/09/94 │ │ Reported In : 30072 RevisedDate : 3/09/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ClaCnv │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ By converting the CLA & INC files in this test file you │ │ will find that the Screen Structure is not placed into the │ │ converted CLA. It magically disappears. │ │ However, by moving the structure where KLA_REC.INC is │ │ included to be ABOVE the SCREEN it will be converted │ │ properly! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4079 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/09/94 │ │ Reported In : 3007 RevisedDate : 3/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When deleting a large number of records in one directory │ │ then pressing uparrow an xtrace occurs see xtrace file. │ │ 4079.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4081 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 3/09/94 │ │ Reported In : 3007 RevisedDate : 3/09/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : BASIC Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3007.1 Using the NAME attribute on a BASIC file crashes the │ │ system │ │ R&D: WOKOMM. I need an example showing this │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4082 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/09/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Arthur Svensson 71554,3162 MSG#:58983 │ │ If you use a Double border on a Dropdown menu with a │ │ Separator the border to the left of the separator is │ │ trashed. This only happens with the double border track. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4083 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/09/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jim Morgan [Mitten] 72371,2444 MSG#:59020 │ │ In 3007.1, When adding a report control field, the system │ │ requires a USE field. However, a PARAMETER should be │ │ sufficient and a USE should not be required. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4084 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/09/94 │ │ Reported In : 3007 RevisedDate : 3/09/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ see test file provided-- when you mouse click onto the │ │ repeat structure the on to the radio buttons you cannot tab │ │ to the repeat structure. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4085 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/09/94 │ │ Reported In : 3007 RevisedDate : 3/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ using ebrowse for an example: │ │ browse display totals: │ │ the first and third options have total fields that display │ │ correctly as you go in but not after you change a record. │ │ R&D: Fixed in 3007.2 (Clarion driver bug) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4086 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/09/94 │ │ Reported In : 30071 RevisedDate : 3/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Larry Teames 73150,104 MSG#:59172 │ │ 1. Create a 30 line GUI screen in VGA MODE (this is very │ │ important) 2. Place an "IMAGE as Button" with the top edge │ │ on LINE 1. 3. Execute BorderOff 4. Make and Run 5. Press │ │ the Button 6. Enjoy the show! │ │ Has to do with the "window move" capability and using │ │ line1 for the button. │ │ Larry Teames -- Creative PC Solutions -- AZ CUG │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4087 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/09/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:59162 │ │ 3007.1 Browse template with range limit. If the File has │ │ no records, the update form is presented, if the fille has │ │ records, but none that match the range limit, the browse │ │ retains focus with the Insert button highlighted (no │ │ records in list box). │ │ The browse template should always remain displayed, │ │ regardless of whether records exist in the file. │ │ Example, fileb is range limited to filea, the range │ │ value is not used and the range limit is an input field on │ │ the browse allowing user selection to filea. The input form │ │ is presented when no records exist, the range limit field │ │ has not been completed and is zero. The range limit │ │ field is NOT an input field on the form, it is supplied │ │ from the browse (which is zero at this time). │ │ Jerry L. Petri │ │ Practical Computing Group │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4088 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/10/94 │ │ Reported In : 30071 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in the great plains dictionary a user reported that in the │ │ order entry file the decimal fields should be defined as │ │ pdecimals │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4089 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/10/94 │ │ Reported In : 3007 RevisedDate : 3/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When I place a field on a report, and I click on the down │ │ arrow next to the "Use:" field, I can only choose from data │ │ that was defined in the dictionary. I cannot choose from │ │ Global or Local data. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4090 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/10/94 │ │ Reported In : 3007 RevisedDate : 3/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ collating sequences for files that will be accessed in 2.1 │ │ and 3.0 do not work properly see file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4091 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/10/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Princen 100276,2655 MSG#:59198 │ │ My last message probebly scrolled. I responded to your │ │ answer on NEWPTR. This is what I find a bit unacceptable: │ │ I have a browse with a file with a non unique key. │ │ When I add a record with a key value that already │ │ let's say 20 times exists then my selector bar stands on │ │ the first one in the list and not on the one I just added. │ │ Did I add the record or .......... This is what I call │ │ confusing. │ │ Majodi Ploegmakers │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4092 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/10/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Martin Wehlou (Cactus) 72047,2444 MSG#:59279 │ │ Minor bug in application tree, module view. Batch 3007. │ │ Pick any module, enter to change module description. │ │ Changing just the case of the text will not update the │ │ view, you have to add or delete characters to make the │ │ program acknowledge the change. │ │ Example: │ │ A module with the description 'something', change that to │ │ 'SOMETHING' and the change won't "take". │ │ -- Martin [Cactus Computing bvba - Belgium] │ │ From Greg_W: I duplicated this problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4093 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/10/94 │ │ Reported In : RevisedDate : 3/15/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ASCII Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ PUT(file,1) will corrupt memory if you have previously read │ │ far enough down the file such that the read buffer no │ │ longer contains bit 0 │ │ R&D: Test program ASCIIPUT added to test suite │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4094 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 3/10/94 │ │ Reported In : 3007 RevisedDate : 3/14/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports in 7105 templates - in the FORM template, │ │ retain record does not work, "missing autoinc add field" │ │ R&D: Fixed in 3007.200 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4095 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/10/94 │ │ Reported In : 30071 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard M. Bri~linger 100120,1622 MSG#:59434 │ │ After installation of templates C7105 and recompilation of │ │ a project the following problem came up: I have declared a │ │ global variable │ │ GLO:WEIGHT, SHORT, display picture @N5. , range limits 1 │ │ to 1000 │ │ The SCREEN template generates the following code: │ │ IF ~INRANGE(GLO:WEIGHT, 1, 1.000) then │ │ (error handling) │ │ END and so, all values other than 1 go into │ │ error-handling ( 1.000 = 1 ! ). I then removed range limit │ │ checking from the declaration of GLO:WEIGHT, but after │ │ recompilation, the code for range limit checking - and so │ │ the bug - was still there. I had to erase all .cla │ │ files to force CDD to re-genereate the source code. │ │ Richard M. Brisslinger, Tutzing, Germany, CDD 37105 + GUI │ │ Not reproducable with 3007.2 templates. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4096 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/10/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Compiling the test application in the Overlay modle, this │ │ report structure is causing and overlay loader failure. │ │ The porblem is at runtime during a VIEW of the report. │ │ 1. Unzip 4096.zip │ │ 2. Make and run group.app using the overlay model │ │ 3. Select Reports │ │ 4. Select Members │ │ 5. Select Master Listing │ │ 6. Destination Screen │ │ 7. Overlay Loader Error │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4097 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/10/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jim Grotjan 72451,75 MSG#:59541 │ │ I'm sure you've already heard this before, but here it is │ │ again. If you set up a browse on a non-unique key (i.e. │ │ 'Name'), but you want to do a lookup by a unique key (i.e. │ │ 'I.D.#'), you cannot do it if if there is more than one │ │ record in the file with the non-unique key. Browse will │ │ always select the first match of the duplicated non-unique │ │ key. It seems that this could be solved, even if it │ │ required passing an additional parameter to Browse │ │ (POINTER(FILE)). It seems a shame that a potentially │ │ great product has, in some areas, less functionality than │ │ its predecessor. │ │ From Greg_W: Similar request in bug 4091. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4098 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/10/94 │ │ Reported In : 3007 RevisedDate : 3/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when running the editor from the dos prompt;;; │ │ With no files loaded in the editor, press the left mouse │ │ button on the file pulldown and drag it to edit. This │ │ action should take you to the dos prompt. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4099 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/11/94 │ │ Reported In : 30071 RevisedDate : 3/25/94 │ │ Fixed In : 3008 Status : Tested/OK │ │ │ │ Section : BASIC Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The rereading of the same record problem occurs if you do │ │ something like │ │ LOOP │ │ next(file) │ │ pointer# = POINTER(file) ! debug stmt │ │ if errorcode() then break . ! at eof? │ │ ..... │ │ END │ │ The call to POINTER clears the errorcode though the LRM │ │ indicates that POINTER │ │ does not post any errors. So you get caught in an infinite │ │ loop, and the last │ │ record is read again and again. │ │ Cindy Cohen │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4100 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/11/94 │ │ Reported In : 30071 RevisedDate : 3/11/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Gregory C. Bailey 76615,1350 MSG#:59700 │ │ Since the BUILD feature is useless for btrieve files. Why │ │ not change the Convert file option to look for the output │ │ file being a btrieve file and not including the BUILD │ │ command in the generated program. │ │ From Greg_W: Maybe we could have the code generate a prompt │ │ for whether to BUILD the file after the conversion is │ │ performed (just an idea). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4101 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/11/94 │ │ Reported In : 30071 RevisedDate : 3/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The DECIMAL statement excepts 15.2 as a valid length. Is │ │ it valid? There is a sample in 4101.ZIP. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4102 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/11/94 │ │ Reported In : 3007 RevisedDate : 3/11/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports -- reg no :207934 /\ relational contrains │ │ accross a WAN 56kb (novell) locks up his machine and if you │ │ wait about 15 minutes you get an error 88 incompatible mode │ │ errror │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4103 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : RB DateReported : 3/11/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Reports are viewed on screen when "File" is selected. │ │ R&D: Fixed in 3009 template release │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4104 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/11/94 │ │ Reported In : 3007 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports that option string fields with required │ │ attribute can be left with out a value unlike any other │ │ field type. Also the Back tab does not move backwards off │ │ the option string. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4105 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/11/94 │ │ Reported In : 3007 RevisedDate : 3/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User reported -=- When there is more than one primekey for │ │ afour componet autoincrementing key only the first is being │ │ check the second and third is not even being looked at. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4106 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/14/94 │ │ Reported In : 30071 RevisedDate : 3/14/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ben Coleman 73742,746 MSG#:59940 │ │ >> What exactly do you mean by REVISED?? Do you want this │ │ text file in >> some other format other than ASCII and │ │ WP5.1 or are you saying that when >> you print it it │ │ doesn't print correctly? │ │ I think he's saying that TEMPLATE.DOC as it is │ │ now(at least for those of us who went from 3006 to 3007 via │ │ patches, I haven't looked at what's on my 3007.1 disks) │ │ reflects the 3006 templates, not the changes made in │ │ 3007(and following). This is something I noticed also - │ │ all of the other files in t\CLARION3\DOC subdirectory show │ │ a date stamp of 1/17/94 or later - TEMPLATE.DOC shows a │ │ date stamp of 10/21/93, same as it was for 3006. │ │ CLARION.TXT seems to have been updated with the template │ │ changes since 3006, TEMPLATE.DOC hasn't. │ │ Ben │ │ There is 1 │ │ Reply. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4107 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/14/94 │ │ Reported In : RevisedDate : 3/14/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Allow Truncated files to be created by the Btrieve driver. │ │ R&D Note: Can do via /TRUNCATE=[ON|OFF] switch │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4108 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/14/94 │ │ Reported In : 30071 RevisedDate : 3/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ken J Horii 76340,1234 MSG#:59773 │ │ Track character is browse source is not aligned after the │ │ comment !Generate Procedure. │ │ The first insertion of !Generated Procedure causes the │ │ double bar "||" to be written two(2) columns, too much, to │ │ the right. However, the second occurrance of ! Primary │ │ Processing File DOES NOT alter the original position of │ │ "||"and keeps the CopyRight Box intact. I did not search │ │ which template file this occurs in! │ │ R&D: This is a comment block problem, due to label sizes. │ │ This is certainly not a bug. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4109 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/14/94 │ │ Reported In : 30071 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: RONALD B. PARKS 74750,2212 MSG#:59849 │ │ Attempt to delete a parent fails because children are │ │ present. The parent is held, it should be released. There │ │ is not reason to hold the parent on a failed deletion │ │ attempt? │ │ Fm: Greg_W: This is similar to Bug# 3789 which is logged │ │ against the Clarion Driver. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4110 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The display statement will clear data that is in a PSTRING │ │ after the specified length of that PSTRING. For example, │ │ if the length byte of a PSTRING is 15, and the field was │ │ defined as a max length of 30, everything after the 15th │ │ position would be cleared from the record buffer after a │ │ DISPLAY statement was isssued. However, this is not good │ │ because if there was a key on that PSTRING, the POSITION │ │ statement will use all 30 characters in the PSTRING to give │ │ that records' unique position in the file. Since the │ │ BROWSE template relies so heavily on POSITION, browse does │ │ not work. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4111 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ International Sorting is not functioning. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4112 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Buffering Needs to be added to APPEND. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4113 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30071 RevisedDate : 3/15/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ken J Horii 76340,1234 MSG#:59812 │ │ 1) CLARION.RED will *NOT* redirect BACKUP FILES to the │ │ \BKP subdirectory. │ │ 2) CLARION3.EXE will *NOT* execute the CONTACTS.EXE in the │ │ \BIN subdirectory. │ │ 3) CLARION.APP will *NOT* allow me to make the PATH │ │ (drv:\subdir) a variable from a configuration file *.INI or │ │ *.CFG. │ │ Greg, the above is the cause of all my current questions │ │ forCDD3.007.105. Should you and Bruce find all this trivial │ │ andbeyond the scope of CLARION DATABASE DEVELOPER please │ │ informme of you decision and I will quit! │ │ TIA... KJH 10MAR94 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4114 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/16/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : VGA Color Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I've recently incorporated the VGA Color Kit into one of │ │ my apps and now get │ │ a compiler warning: │ │ "Warning: ASCII_IDtag is duplicated, files involved are │ │ dovascii.lib and │ │ dovrgb.lib" │ │ "Warning: ASCII is duplicated, files involved are │ │ dovascii.lib and dovrgb.lib" │ │ R&D: This is caused by linking the ASCII driver into the │ │ %clapfx%RGB.LIB file. The driver is needed by the LOADRGB │ │ procedure which reads the user's customized color file into │ │ the program. The next release of the VGACOLOR Kit will not │ │ link the ASCII driver into the lib; instead, users will │ │ have to explicitly link the driver along with the VGACOLOR │ │ lib. │ │ In the meantime, there are three approaches: │ │ (1) Ignore the warnings. │ │ (2) Remove the explicit link to the ASCII driver in RGB.PR. │ │ If done, the link still needs to be made for dynalink and │ │ extendll models in RGB.PR, as is done for │ │ %clapfx%LLRGB.LIB. This also ensures that the latest ASCII │ │ driver shipped with CDD is used. │ │ (3) Remove, if possible, the explicit link to the ASCII │ │ driver added in the user program (usually not possible in │ │ Generator). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4115 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30071 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Arthur Svensson 71554,3162 MSG#:57800 │ │ How to generate a GPF in Cla3.701 at will: │ │ 1- At CDD Main Menu select 'Clarion' │ │ 2- Select 'Load Help' │ │ 3- At Load Help window make sure browse is not completely │ │ filled (I did this in C:\Clarion3 which has only about 6 │ │ help files) │ │ 4- Place mouse cursor on the vertical slider & │ │ press left mouse button │ │ 5- Holding down button, slide down the vertical scroll │ │ area until you reach the bottom (down) arrow (the slider │ │ will not move). │ │ 6- When the cursor hits the bottom arrow the files listed │ │ in the browse will disappear. │ │ 7- Release the mouse button 8- Press the LOAD button │ │ ...... CRASH!!! This also happens with the │ │ App, Dict, Text, etc Load windows. It will not occur if │ │ there are enough files listed in the browse to fill it. │ │ My copy of Clarion 3 was loaded with fresh diskettes (no │ │ patches). │ │ From Greg_W: I duplicated this xtrace. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4116 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/15/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ For any given field which has been #FIXed in %Field, there │ │ does not seem to be a %Symbol allowing one to verify the │ │ following: │ │ 1) Validity Checks Off 2) Cannot Be Zero Or Blank 3) Must │ │ Be True Or False │ │ Any ideas for accomplishing this WITHOUT %Field being used │ │ on a screen? │ │ Douglas │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4117 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/15/94 │ │ Fixed In : Status : Question │ │ │ │ Section : Operating System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 52755 S8/3.0 Support │ │ 31-Jan-94 01:42:57 │ │ Sb: CDD & NT │ │ Fm: D. Fast 71652,2205 │ │ To: Debby Herman 72662,475 │ │ Hello Debby, │ │ I am looking for the DOS Settings to run CDD (Mostly │ │ Editor.Exe) under Windows NT. I will beneeding the same for │ │ the Extended and Overlay model applications under NT as │ │ well!! │ │ It appears that there is No set of rules available and │ │ C3006 works where C3007 may Not!! It is frustrating to be │ │ constantly 'tweaking' the environment for either the │ │ application or the development environment!? │ │ Is it possible to get a formally published set of rules for │ │ the development environment; Overlay and Extended models of │ │ the application? I am (seemingly) never in the right │ │ environment without rebooting to a straight DOS │ │ environment and THAT is a reduction in productivity on a │ │ workstation which will easily support one or more compilers │ │ running under an advanced OS (NT or OS/2); yet, I must have │ │ THAT kind of luck with Clarion (both apps and IDE). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4118 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 60278 S8/3.0 Support │ │ 14-Mar-94 22:35:39 │ │ Sb: PDecimal sign nibble bug │ │ Fm: Jeff Moyers 70254,2434 │ │ To: Greg Whitaker [Clarion] 76711,1035 (X) │ │ Greg, │ │ There is an anomoly concerning PDecimals in 3007.1 & 3007.2 │ │ extended model. │ │ (Other models may have the same problem.) When a PDecimal │ │ is implicitly │ │ initialized (to 0), it is properly initialized and the sign │ │ nibble contains 0. │ │ But, when a PDecimal is --explicitly-- assigned a value of │ │ 0, by any possible │ │ means, the sign nibble is being set to indicate positive │ │ (F). The math Library │ │ routines have no problem with this, so it would appear to │ │ be a non-issue... │ │ HOWEVER, this is a big problem, and I'll tell you why. │ │ When this PDecimal is │ │ stored in Btrieve, the invalid sign nibble goes with it. If │ │ this field is part │ │ of a key, in particular if it is a Manual key segment with │ │ a Null value of 0, a │ │ key segment value of zero causes an index to be created │ │ because the value is │ │ not really zero, it's 15! Now, in my case, a Btrieve │ │ accounting file depends on │ │ this structure to quickly read the 20% of transactions that │ │ have non-zero │ │ balances. Weeeeellll, with this PDecimal bug, EVERY │ │ transaction is non-zero to │ │ Btrieve, even if it still looks like zero to CDD. Please, │ │ please, please, this │ │ must be fixed! I'm working on a workaround, but it's not │ │ very pretty.... │ │ Jeff │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4119 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30071 RevisedDate : 3/15/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : REPORT ENGINE │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:59979 │ │ Consider a report band. The first field is customer name, │ │ string(25). 25 chars is too long, make the thing a text │ │ field 20 cols by 2 lines. When the report prints, the │ │ first character of the string is printed at character │ │ postion 26 in the text field. │ │ For example: │ │ This is a very long name! │ │ should be formatted as: │ │ This is a very long │ │ name! │ │ In fact it prints as: │ │ This is a very long │ │ name!T │ │ And... │ │ Short Name │ │ formats as: │ │ Short Name │ │ S │ │ Cheers! Have a good weekend! │ │ Rob from Chariot │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4120 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : VID │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 15-Mar-94 06:53:49 │ │ Sb: 3007.2 debug problem │ │ Fm: Jerry L. Petri 72633,3345 │ │ To: sysop (X) │ │ uploaded/installed the 3007.2 patch, found the following │ │ problem when running │ │ debug from designer on a 512K VGA card. Used the example │ │ DEMO.APP for this test, overlay link. │ │ Most graphic screens have a line of garbage on line 12 or │ │ 13 on graphics │ │ screen, does not always happen if the previous screen was a │ │ full text screen. │ │ If there is a text screen over the image screen, the mouse │ │ cannot be moved │ │ below the underlying garbage line on the screen. │ │ This does not happen in running the final EXE and does not │ │ happen on 1MB VGA │ │ screens. │ │ If you need additional testing/information, please contact │ │ me. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4121 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/16/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Once code is added to the PRE-PRINT and code is added to │ │ the POST-PRINT source, the code that was in PRE-PRINT gets │ │ erased. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4122 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/16/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In 'must be numeric range', if a byte field has a picture │ │ of@P##%P, the values in the 'must be in numeric range' │ │ change, i.e., HIGHEST = 60, LOWEST = 20 will revert to │ │ HIGHEST = 6, LOWEST = 2 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4125 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 3/16/94 │ │ Reported In : 30072 RevisedDate : 3/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User reports the CENTER function returns a null when it is │ │ passed a literal larger than the target variable │ │ Also returns null if passed 2 variables which are │ │ concatenated, regardless of target size │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4126 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 3/16/94 │ │ Reported In : 30072 RevisedDate : 3/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User reports CHANGE function does update correctly, but │ │ does not DISPLAY to the screen │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4127 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 3/16/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user experiences funny colors in the message attribute in a │ │ form, and then system locks. Occurs in a form after │ │ validating a field, procedures are about 6 levels deep. It │ │ only happens in protected mode, and it did not happen in │ │ 3007.1. User tried swapping video cards, with QEMM, │ │ without, etc., with same results. The app is approximately │ │ 1 meg, ~ 54 modules │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4128 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/16/94 │ │ Reported In : 7.2 RevisedDate : 3/16/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ test suite:20remov.exe is reporting a floating point error │ │ during the OPEN(file). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4129 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/16/94 │ │ Reported In : 30072 RevisedDate : 3/16/94 │ │ Fixed In : Status : Question │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ although this example may be silly - what does this error │ │ message mean: │ │ program │ │ queue queue,pre(htb) │ │ dds string(150) │ │ dsc_str string(30),dim(5),over(htb:dds) │ │ . │ │ code │ │ return │ │ compile error: Error: Embedded OVER must name field in same │ │ structure │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4130 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : SF DateReported : 3/16/94 │ │ Reported In : 7.2 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you start a transaction, then open a btrieve file that │ │ is in the transaction with a different file handle, then │ │ close that second file you get a btrieve error code 41. │ │ This did not happen with 3007.1 │ │ R&D: This was because 3007.1 was not returning the error │ │ code. Btrieve include ALL files in transaction processing. │ │ So any close is illegal in the middle of a transaction. │ │ Documentation has been updated to indicate this variation │ │ from the Clarion documentation. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4131 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When running options.cla the virtual memory settings screen │ │ has 4 options: OFF, DISK ONLY, EMS, XMS. If I choose DISK │ │ ONLY, it generates a line in the ini file like the │ │ following: CLAVM=DISK ONLY etc.... What is DISK ONLY? I │ │ think it should be generating NOEMS. If DISK ONLY is │ │ correct it is not documented anywhere. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4132 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 3/17/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Press CtrlF on the first line of the report. The │ │ formatter of the report chokes and returns an error on the │ │ Printer() attrubute due to the fact that it contains ending │ │ parenthesis character ")". If you remove the ")" the │ │ formatter has no trouble with it. If you are trying to │ │ format a report in the editor as part of appgen (in a │ │ SOURCE procedure) and you run into the above problem, you │ │ can cause an xtrace as soon as you close the red error │ │ window. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4133 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 3/17/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Create a report in the editor with the │ │ Width(11111111111111), 14 characters. This is hand code │ │ and cannot be done in the Report Fromatter. If you do a │ │ CtrlF on this report will cause an Xtrace. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4134 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the report formatter, it allows you to add a '' │ │ character as a track character, when the application is │ │ compiled, there are numerous error messages such as; │ │ 'Error: String not terminated'. The double music note │ │ works fine. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4135 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Several problems with text fields: │ │ Is IMM valid on a TEXT field? LRM page 8-43 states it is │ │ valid but page 8-32 does not specify it is a valid │ │ attribute. In the screen formatter it is also dimmed. If │ │ you type it into the screen structure and compile - no │ │ compile error is given. │ │ If the text field is in INS mode, it will complete as if it │ │ had an IMM attribute. │ │ If the text field has the INS attribute set, it does not │ │ come up in INS mode. │ │ You cannot have a character in the last column of a line │ │ in a text field, it will always wrap to the next line. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4137 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : REPORT ENGINE │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A line in the header section has the "Supress" attribute on │ │ it(line 1). Just one variable (a string) exist on that │ │ line. The very next line (line 2) is blank. If the │ │ variable on line 1 is empty, the report prints correctly. │ │ If there is data in the variable on line 1, it prints, │ │ however, the blank line (line 2) does not.. See test file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4138 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you use DO to call a PROCEDURE instead of a ROUTINE, │ │ your machine will reboot during compilation. This is not │ │ uncommon among users, and perhaps an error should be │ │ generated. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4139 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/17/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Overlay loader fatal error: 8501 │ │ to duplicate create a large txt file (about 15,000) records │ │ and use the view template to view the file. (overlay model) │ │ I duplicated this error because an end user recv'd it when │ │ trying to view a report on the screen │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4140 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/18/94 │ │ Reported In : 30072 RevisedDate : 3/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CLAMATHTRAP and CLAMEMTRAP need to be documented in │ │ runtime.doc │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4141 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 3/18/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Select Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Select not selecting when enter is hit. │ │ R&D: Repaired in 3009 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4142 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/18/94 │ │ Reported In : 30072 RevisedDate : 3/18/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : DBase III Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when building a key on dbase iii file, end user recieved a │ │ null expression error. This occurred when a key field did │ │ not contain a value. Dbase supports this. │ │ R&D: Need more info. What type of key? An example would │ │ be very helpful. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4143 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/18/94 │ │ Reported In : 30072 RevisedDate : 3/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In Generator, Editor & Report Writer if I have the │ │ following: │ │ Detail Detail │ │ Row(2,1), Control('12 CPI') │ │ Col(5), String('test this stuff') │ │ <more stuff> │ │ And then I save the structure. Go back into the structure │ │ and add ANOTHER Control field AFTER the first control and │ │ Before the Text. You will find that after saving the │ │ Structure the 2nd control is no longer in the structure. │ │ This needs to be checked when a field is place after the │ │ controls too! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4144 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 3/18/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : CLARION.APP │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard M. Bri~linger 100120,1622 MSG#:60533 │ │ Hello, there seems to be a buggy situation when viewing a │ │ report on screen. The problem comes up if you - use the │ │ variable REPORTDEVICE as parameter for the DEVICE() │ │ attribute of the report (this happens by default in │ │ CDD) - use REDIRECT and VIEW to view the report on screen - │ │ and this in a directory with a long pathname │ │ what happens is: │ │ REDIRECT generates a temporary filename │ │ preceeded by the path; in my case │ │ 'C:\CLARION3\EASYMAIL\RPT00001.$$$' and puts this filename │ │ into GLO:FILESPEC The report then │ │ copies GLO:FILESPEC to REPORTDEVICE As REPORTDEVICE │ │ is declared in CLARION.APP as a string(30), the filename │ │ is truncated to 'C:\CLARION3\EASYMAIL\RPT00001.' So ,the │ │ report creates a file 'C:\CLARION3\EASYMAIL\RPT00001' The │ │ VIEW procedure now tries to open the file with the name │ │ given in GLO:FILESPEC and stops with the errormessage │ │ 'Cannot open file 'C:\CLARION3\EASYMAIL\RPT00001.$$$' │ │ Short │ │ consequence of the long story: the variable REPORTDEVICE, │ │ declared in CLARION.APP in REPORT and PRINT must be │ │ string(64). │ │ Richard M. Brisslinger, Tutzing, Germany, CDD30072 + │ │ GUI │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4145 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 3/18/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Robert E. Hoag 73201,2607 MSG#:60552 │ │ I have a field declared as byte that has a 'must be in │ │ list'validity check. Radio buttions are created on a │ │ screen field, along with other variables that are │ │ declared as strings (with 'must be in list'). I have │ │ added a button that sets these fields to a default │ │ value, by making assignments the variable, then │ │ using DISPLAY. All of the radio buttons show the default │ │ selection except for the one that is declared as a byte (2 │ │ integer byte). Is this a bug? What's going on? │ │ Suggestion from Greg_W: Disable "Must be in List" for any │ │ field type other than STRING, since the option structure │ │ created for it's implementation only works with STRINGs. │ │ Either that or add something to the on-line help │ │ explaining the fact that "Must be in List" creates an │ │ Option structure that only works for STRINGs. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4146 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 7.2 RevisedDate : 3/18/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A call to getch() crashes. The cause for this is that │ │ stdin is not initialised in the Clairon initialisation. │ │ Workaround: call the following piece of C code before │ │ making any call that requires stdin. │ │ FILE *_stdin; │ │ _stdin = fopen("CON","r"); │ │ _iob[0] = *_stdin; │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4147 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : RB DateReported : 3/18/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Group footer totals print as 0's. Report Totals "seem" to │ │ work OK. │ │ R&D: User was tallying on Group rather on Body │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4148 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 3/28/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : ASCII Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:60349 │ │ Problem 1: │ │ In 3007.2 report template, if you have a formfeed at the │ │ end of the page and use the view template to display on │ │ screen you get AUTO-REBOOT from DOS, and a locked up window │ │ in WIN 3.1 (CTRL_BREAK) will exit OK. This appears to │ │ happen in all reports that happen to have a VALID printer │ │ name in the report properties. │ │ Report prints to printer OK. │ │ To test change the example chekbook.app, check register │ │ report to add a formfeed in the page footer, recompile, run │ │ and display on screen and guess what - AUTO-REBOOT. Problem │ │ 2: In windows the view template locks up the window upon │ │ display, with or without the formfeed as long as a valid │ │ printer is defined. By valid printer I mean one that is in │ │ the printer.ctl. Select one in the report and then go to │ │ Clarion options, delete the printer from printer.ctl so it │ │ can't match, it runs fine but displays the word "FORMFEED" │ │ on the screen. │ │ QA&E Work Around: │ │ Both problems are in the ASCII Driver. The problem arises │ │ when you place the FF at the end of a line instead on in │ │ COL 1 all by itself. │ │ R&D: Same as 4096 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4149 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 3/18/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:60367 │ │ As of 3007.2, the list template is missing the following │ │ functions to make it more usable. │ │ The list template does not have "Case no records" exit. │ │ The list template does not have Locator capabilities, │ │ need both regular & incremental. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4150 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fadi G. Ashi 74650,1146 MSG#:60630 │ │ I downloaded release 7.2 yesterday and I found a new bug if │ │ you are compiling under protected mode. If you trye to │ │ build a dynamic index for an empty file you get an xtrace. │ │ If you compile under overlay or static the program will run │ │ fine. The work around is fairly easy but I thought you │ │ should know about it. Sincerely, │ │ R&D: Do not know whih driver this is. Will create a test │ │ program to test all drivers │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4151 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/18/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : View Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you display a report with the view template and the │ │ report has a formfeed in the page footer in a column other │ │ than the first column, you will lockup or xtrace. │ │ I am not sure where this should be directed. │ │ see example program │ │ 4151.zip │ │ added note cs message │ │ Based on my tests, the 3007.1 ???ASCII.LIB & ???ASCII.DLL │ │ files will will work okay with 3007.2 (as an interim work │ │ around, of course). Larry Teames │ │ R&D: Same as 4148 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4152 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 3/18/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User uses bios com function (c-runtime library bio.h) to │ │ interfact with comm port. - gets 'Link error: BiosCom is │ │ unresolved in file - only occurs when using RTL's │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4153 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/21/94 │ │ Reported In : 30071 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Dan Luther 71121,417 MSG#:60647 │ │ I would like to see the following additions to Clarion: │ │ A way to view the database dictionary within the Clarion │ │ editor, cut and paste would be nice. Perhaps a way similar │ │ to the "Choose Variables" in the screen layout box. That │ │ waythe database layout, local and global variables would │ │ alwaysbe on hand for reference. │ │ A nice way to print out the local and global │ │ variables when defining them. │ │ Better support for "OVER" and "EXTERNAL" │ │ attributes in the Data definitions screen. Support in VID │ │ for variables not declared within the Data screen (i.e. │ │ in an EMBED section). The end-user report writer (that │ │ was promised long ago) │ │ Perhaps external editor support? I use Multi-Edit 7.0 │ │ and have written some support macros for Clarion; these │ │ are nice; A command-line Clarion compiler. A full set of │ │ Clarion commands, │ │ procedures, and goodies in the on-line help. │ │ Slowly but surely, I'm │ │ being "weaned" from the application designer; It serves its │ │ purpose well, but I just can't think of anything │ │ marketable that can be completely written in the designer │ │ just using templates. │ │ I'd like to add the following: │ │ SQL support. Think about this for a minute, read the first │ │ page any issue of PC-WEEK or whatever weekly computer │ │ newspaper you get, and think of the │ │ potential profit from a(n) SQL driver. │ │ The Paradox 4 driver (please...) │ │ Support for user-defined data structures. Although this │ │ would require some kind of API, it would simplify a great │ │ deal. I started some time ago on a field input routine that │ │ would have a rich input mask. Although I never completed │ │ it(writing it in Clarion was... well, an exercise in │ │ frustration) I plan on implementing it as a C routine as │ │ soon as I have some time. │ │ In addition to the support for "OVER" and "EXTERNAL" │ │ attributes in data screens. I'd like to see support for │ │ "LIKE", and better handling/copying │ │ of "GROUP"s. Here's the scenario: │ │ A file called "CUSTOMERS" has 2 phone number fields: │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4154 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/21/94 │ │ Reported In : 30071 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jeff Moyers 70254,2434 MSG#:60670 │ │ The report formatter from Editor or CDD has an anomaly. A │ │ Row statement with more than 2 digits in the column │ │ parameter is truncated to 2 digits. For example: │ │ SomeField Row(3,122) │ │ is interpreted as SomeField Row(3,12) │ │ If the file is saved it will be written back to │ │ the file incorrectly as well. You have to manually correct │ │ it every time you come out of the editor. Col(122) is fine. │ │ I think the editor is assuming a max of two places for the │ │ column parameter. Row(3, 122) will produce │ │ compiler error "Invalid character". (Note the space after │ │ the comma) It has been this way since the beginning of CDD. │ │ Am I the only one to ever report it?? Thanks! │ │ Jeff │ │ From Greg_W: I duplicated this situation OMM. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4155 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/21/94 │ │ Reported In : 30071 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralph Johnston 71033,135 MSG#:60729 │ │ To the Bug-Catchers, There appears to be an interoperability │ │ difficulty (bug for short) with the STATUS('LPTx') │ │ command. (This is not the problem with CAPTURE, although │ │ itmay be related.) │ │ Bug #1: Under DRDOS 6.0, STATUS('LPTx') will always return │ │ a '1'. │ │ Bug #2: If you then send characters to a not-ready port │ │ (because the status said it was OK!), it will time out │ │ with a "Hardware Problem _Managment_ Window" (notice the │ │ misspelling of Management). │ │ Bug #3: Under OS/2, STATUS('LPTx') will also always │ │ return a'1'. That is using OS/2's version of "DOS", not a │ │ boot of a "real" DOS. The difference is that sending │ │ characters to the port will not cause any errors, as OS/2 │ │ seems to gobblethem up and send them to the bit bucket. I │ │ realize the bit bucket thing is OS/2's │ │ problem, but the STATUS() still doesn't work right. │ │ I'm using 3.0, version 3007, template version 104/105, │ │ paragraph 11, subparagraph 499.95... *grin* ..Ralph │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4156 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ after putting 3 printer controls in a row on the same line │ │ in a the body, after saving the format and returning, the │ │ last printer control disapears. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4157 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Duplicate │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using the result of a LIST Formula Class in a SUM Formula │ │ Class does not work properly. │ │ R&D: Duplicate of Bug # 3625 (part 1) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4158 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reported - when a procedure is mistakenly called as a │ │ routine the compiler will lock up when optimizing │ │ NCla$PushString. Should this produce a compiler error?? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4159 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ documentation for findfirst/findnext should include a │ │ statement that "all filenames" in directory will be │ │ returnedincluding any that match the attribute passed to │ │ findfirst. User is expecting only entries to be returned │ │ that match the attribute. │ │ ex. using the FA_DIREC attribute, user │ │ expected to only see directory entries, but was seeing │ │ all files including directory entries. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4162 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ using the clarion driver and the send command, this program │ │ will lock when trying to exit. This only happens in │ │ protected mode. Overlay or Real mode works fine. │ │ ts proj 3203 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4161 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using the mouse to move the border in GUI will stop and │ │ Idle procedure from executing. The Idle procedure will │ │ resume operation after the screen is moved. This is │ │ correct, however MOVE needs to be turned off since some │ │ users want the Idle procedure active at all times. │ │ The API library will not turn off movement of the boarder │ │ when GUI is loaded. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4163 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/21/94 │ │ Reported In : 30071 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : REPORT ENGINE │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Guzik 70550,1317 MSG#:60879 │ │ Does Clarion 3.0 Buffer it's Reports. │ │ We are cuurently converting a Clarion 2.1 application to │ │ 3.0. In this application we've written a procedure to │ │ produce our company letterhead thru a HPIII(PCL5-GL/2) │ │ printer using PRINT (string) command. We would use this │ │ procedure in the middle of a report to produce letterhead │ │ on various reports. When we started converting to 3.0 we │ │ tried a similar procedure, but could not get it work │ │ correctly. │ │ From Greg_W: Duplicated and created example, 4163.ZIP │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4164 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when placing a control field on the report, you do not │ │ have the option for overprint next from the control field │ │ screen │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4166 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Using the Btrieve NLM610c and the DOS BREQUESTOR 610e. │ │ If you use the browse template with a range locator field │ │ and try to delete the last record in the range you will get │ │ an 'Unrecoverable Record' Code 19. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4167 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ usesymbols command seems to be ignoring the last set of │ │ symbols in the string (to be exact the "check on" symbols) │ │ since there were 3 characters added for the mouse symbols, │ │ it looks like the last 3 for the check on got pushed out │ │ and now does not get recognized. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4168 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ for a small text file, one larger than 2 screen fulls but │ │ less than 10 of text, with the combination of the elevator │ │ and the editor screen you can Xtrace. But you must be very │ │ deliberate. see file │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4169 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The round() seems to be a little broken see file 4168.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4170 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I never knew I could add individual Project │ │ Statements with the Project Settings windows. (It's not in │ │ the documentation │ │ after all. Grr. Online doesn't count.) I tried it to add │ │ a comment, and it │ │ works--sort of. │ │ Immediately after adding the comment, a quick look at the │ │ project file from │ │ outside the world of CDD shows the comment there nicely. │ │ After a make, the │ │ comment is gone in the external world and messed up in the │ │ CDD world. I had │ │ -- This is a comment │ │ #edit refresh file.cpp │ │ which was turned into (in the IDE world) │ │ -- This is a comment*#edit refresh file.cpp │ │ where the * character looked like a quarter note. This │ │ would make it pretty │ │ easy to miss real project statements buried in comments. │ │ Is this the correct │ │ behavior? │ │ Note form TS - I was able to produce this. Just add a │ │ comment and then the #edit and you will see it makes one │ │ line with both. Debby │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4171 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ : 61540 S8/3.0 Support │ │ 21-Mar-94 16:21:24 │ │ Sb: #61414-#case-insensitive Q sort │ │ Fm: Jeff Moyers 70254,2434 │ │ To: Greg Whitaker [Clarion] 76711,1035 (X) │ │ Greg: │ │ >> Storing the Upper of the field in another queue field │ │ is │ │ >> about the best suggestion I can think of. │ │ Thanks for your reply. This solution will work, BUT look at │ │ its potential │ │ costs. Consider a queue that has a 48 byte Name field that │ │ is your sort key. │ │ If I have a queue with 50,000 records (not at all uncommon │ │ in our application), │ │ and I have to duplicate that 48 byte string for sorting, │ │ that adds (48 * 50000) │ │ = 2,400,000 bytes (2.34MB) to my memory requirements. Yes, │ │ I could trim the key │ │ down some. Yes, I could use a temporary file. Yes, I could │ │ other things. But │ │ the ability to sort the queue case-insensitive is the only │ │ logical _solution_ │ │ to the problem; everything else is a workaround. │ │ In reality, in protected mode (we are), this will │ │ automatically get swapped to │ │ disk if memory is exhausted, but that _really_ slows things │ │ down. Adding │ │ another 4MB (to a base of 4MB) of memory, would cost our │ │ company approximately │ │ $28,000. (200 machines * $140/machine). This can't be that │ │ hard a thing for │ │ you guys to do, and I know I'm not the only person whose │ │ ever suggested it. │ │ Could we at least get it to be considered?!?. Thanks! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4172 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30071 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 MSG#:61342 │ │ Your reference to this use of a list box reminded me that │ │ I've been meaning to request the ability to scroll lock a │ │ list.. If we could lock the scrolling mechanism, it would │ │ save the user from having to press the UP/DOWN arrows 20 │ │ times to initiate movement and navigate the list. │ │ For those instances where record selection wasn't │ │ desireable(e.g., viewing an ASCII file), this new list │ │ attribute/feature would be very helpful. It would │ │ also negate the need for a highlight pointer, │ │ which seems a little out of place when only "viewing" text. │ │ Since the Clarion help system also uses the list box │ │ technique, it would also benefit from scroll locking, │ │ (though hypertext links would need to be enhanced to │ │ include an alternate (and possibly more industry standard) │ │ reference to hot points. │ │ Mabe R&D can give this some │ │ consideration for "a future release of CDD". │ │ Thanks, │ │ Danny │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4173 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I wish I could "Re-Alias", but alas, no such function │ │ exists. Hence this │ │ thread. You see, the problem is that the called function │ │ has no idea what │ │ alias (if any) exists for a given keycode. It can Alias │ │ whatever it needs, but │ │ it can't restore the alias table to its prior condition │ │ upon exit. Then the │ │ calling procedure's aliasing is potentially destroyed. The │ │ calling procedure │ │ could certainly reset any aliases it has set following │ │ _every_ call to any │ │ function or procedure that might reset alieses, but what a │ │ nightmare to try to │ │ maintain that beast. This is, IMO, much needed │ │ functionality, unless I'm │ │ missing something. Thanks! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4174 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30071 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: jeffrey d. kolker 72103,2632 MSG#:61094 │ │ >>After a record is added, using a form, and the user us │ │ returned back to the calling browse list, the new record │ │ is not highlighted. This use to work in 3005 but now it │ │ does not in 3007.2. Did something change that I need to │ │ adjust for in my program, or is this a bug? │ │ >>Do you have a range limit? │ │ I do have a range limit. What I have is a three │ │ field key, in which the combination of the three fields is │ │ unique. The limit on the Validate screen is the first two │ │ fields. All records matching the value of the first two │ │ fields are displayed in order of the third field. │ │ (example Job Department - Job Number - │ │ Ticket Number) All tickets for a particular Job │ │ Department-Number combination are displayed. When a new │ │ Ticket Number is entered, the highlight is placed on the │ │ first ticket number for the Job. It use to │ │ highlight the newly added record in version 3005+. No │ │ changes have been made on my part to the form or validate │ │ procedure since upgrading to 3007. │ │ Is this │ │ normal? Since each Job Dept-Number-Ticket combination is │ │ unique, according to your previous note, the new record │ │ should be highlighted. I hope I made the problem clear to │ │ you (as mud?). Any help would be appreciated. │ │ Thanks. │ │ Jeff Kolker │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4175 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 61600 S8/3.0 Support │ │ 21-Mar-94 20:10:57 │ │ Sb: #61422-3007.2 XTRACE │ │ Fm: Bob Divine 76130,3536 │ │ To: Greg Whitaker [Clarion] 76711,1035 (X) │ │ Greg, │ │ I use a path extender (addtoit) to allow me to increase the │ │ number of characters I can have in my path statement. This │ │ has never presented a problem │ │ with any other application. Here is how I caught this one: │ │ I noticed that when I got the xtrace, I was dumped to a │ │ directory other than the CDD directory where I was running │ │ the 'Update Driver' from. So I started looking at the path │ │ and the environment after the Xtraces. After each Xtrace, │ │ my environment was hosed. I had a bogus path statement and │ │ various bits and pieces of path statements throughout the │ │ environment as if they were SET statements with no SET. │ │ SO...I removed the addtoit statements and went with a │ │ straight dos path statement. NO XTRACE. │ │ But...this module, and I would guess others as some other │ │ problems I was having with Saves in the Editor have gone │ │ away, is jacking with the environment AND SHOULD NOT BE!!! │ │ Here is how you can test this: │ │ 1. You need to have multiple partitions (I have 5) │ │ 2. You need at least one statement in your path that points │ │ to a subdirectory on each of the partitions. │ │ 3. Go to each partition and change to the root directory │ │ ... CD \ │ │ 4. Go to the Clarion directory and run CDD and choose │ │ 'Driver Updates' from the │ │ options pulldown. │ │ 5. Exit Clarion │ │ 6. Change to each partition and see if you are still in the │ │ root directory. │ │ I'll bet you are now in the directory pointed to by the │ │ LAST entry in the path │ │ for each partition. │ │ There is no reason for CLARION to be jacking with the │ │ environment like this!!!! │ │ Bob │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4176 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:60994 │ │ Print layouts (report template and print layout in Batch │ │ template) drops printer control codes. │ │ If you put more than 1 printer control in adjacent │ │ positions on a line with text on that line. Ex., col 1 │ │ (reset) Col 2 landscape on, col 40 text "hello". │ │ If you leave the report layout and come back, the column 2 │ │ landscape on is GONE. │ │ Workaround - either leave a space between printer controls │ │ or don't put any text on the line. │ │ From Greg_W: This is the same as Bug# 3019 reported against │ │ 3006 fixed in 3007, Status: Tested/OK. │ │ I duplicated the problem in 3007.2 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4177 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : ASCII Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Executing a PUT or a GET passed the number of bytes in an │ │ ASCII file will create and XTRACE.TXT file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4178 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Another one from the "BIG K" himself. Here goes: │ │ 1. Place Cursor on the Button. │ │ 2. Press CtrlC │ │ 3. Press ENTER to select "Copy From" │ │ 4. Move "new" button (DO NOT PRESS ENTER!) │ │ 5. Press CtrlC to copy another │ │ 6. Press ESC to abort additional copies │ │ 7. Press CtrlF on the "new" button and notice that it │ │ is NOT actually in the Screen Structure as a │ │ button! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4179 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There is a problem with the USERICON function. If one of │ │ the bytes in the string parameter is a 0, CDD thinks its │ │ the end of the string. I assume a Cstring or similar is │ │ being used. 0 is a valid byte for the string, indicating │ │ all bits off in the bitmapped image. │ │ See example file 4179.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4180 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 MSG#:61244 │ │ I'm wondering if there's not something wrong with the way │ │ the Form's CANCEL button is handling referential │ │ integrity. │ │ Let's say you're adding an Invoice record, who's │ │ primary key is INV:InvoiceNum. When the invoice form is │ │ on the screen, the user starts entering the customer's │ │ name Inv:Address etc., then hits a hot key or a button │ │ to enter detail records. He saves the detail records │ │ then returns to the invoice form. If he now hits the Cancel │ │ button the abort the Invoice form, the Cancel doesn't │ │ delete the Child records that he's just added! │ │ Oh boy! │ │ So the Detail records are orphaned │ │ with an Dtl:InvoiceNum that doesn't exist in the Invoice │ │ file. Worse yet, when a new Invoice is created, the │ │ detail records gets appended to the next customer's │ │ invoice (since he'll reuse the deleted number). He won't be │ │ too happy about that.<g> │ │ Since the form is │ │ deleting the Child records properly when the Invoice is │ │ DELETED, the Child records MUST be also be deleted when │ │ a record is being added then cancelled. Otherwise you run │ │ the risk of circumventing referential integrity. │ │ What do you │ │ think? │ │ Barry... │ │ There are 2 │ │ Replies. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4181 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Total field do not update on an add/change or delete unless │ │ you have hot record checked on. │ │ This is the workaround I have devised. Waiting for Tom to │ │ reply. │ │ To fix the problem in the 3007.2 browse template where the │ │ total │ │ fields do not update after the add/change/delete, add a │ │ display │ │ statement to the browse.tpx. │ │ UpdateProcedure ROUTINE │ │ #INSERT(%TotalBeforeUpdate) │ │ #EMBED('Prior to Update Procedure') │ │ %UpdateProc │ │ #INSERT(%IsUpdateSuccessful) │ │ #EMBED('After Update Procedure') │ │ #INSERT(%TotalAfterUpdate) │ │ #INSERT(%RestoreRangeFields) │ │ SELECT(?List) !line 447 │ │ display !add this line of code in template │ │ #ENDIF │ │ R&D: Fixed with 3009 Templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4182 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : GUI Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Arthur Svensson 71554,3162 MSG#:61302 │ │ If you have a GUI executable, running it from within the │ │ IDE creates a 'Black Hole' upon return to the IDE. To │ │ reproduce this: │ │ 1- At IDE select PROJECT -> RUN │ │ 2- Exit from the GUI executable │ │ 3- Upon return to the IDE the mouse cursor will not │ │ be visible │ │ 4- Move the mouse │ │ 5- The mouse cursor will now be visible, BUT a │ │ 'Black Hole' will be visible where the invisible mouse │ │ cursor was located │ │ 6- Moving the mouse around doesn't clear the 'Black │ │ Hole'; pressing PG_DN & then PG_UP will clear the blemish I │ │ don't know if this blemish will corrupt anything │ │ Fm:Danny L. Joe: │ │ For what it's worth, I've also seen this anomoly occur when │ │ the IDE, in 50 line mode, runs an EXE which switches to 25 │ │ line mode, so it's not isolated to the GUI. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4183 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Response │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Brian P. Smyla 76560,145 MSG#:61259 │ │ When using the Validate template and entering a display │ │ key,if the key name is longer than 16 characters, the │ │ extras gettruncated, and an error occurs during compile. │ │ Example: I have a key called OccurrenceCodeKey. When I │ │ insert this intothe display key in the template, all that │ │ will fit is Eve:OccurrenceCodeKe. This is what ends │ │ up in the source code at compile time, and you can see │ │ what havoc that would wreak. │ │ Also, the formula generator will not │ │ take a trailing space in a constant text entry. The │ │ trailing space is dropped no matter what you do. Kind of │ │ inconvenient at times, and shouldnt be too difficult │ │ to fix in a later version. │ │ R&D: 1. Known problem in 1... the dictionary editor allows │ │ for a key name length greater than 20 characters (prefix+ │ │ keyname). │ │ 2. A vertical bar | can be placed in a constant text │ │ entry in the formula generator to enclose any number of │ │ trailing spaces to the left. The vertical bar will be │ │ stripped out at source generation time. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4184 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : CPD21 Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: KC Shore 76470,3544 MSG#:61871 │ │ Yes I am using the 3007.2 templates when there is an auto │ │ incrementing field you get and air on compile that says │ │ auto not defined. │ │ From Greg_W: I duplicated this problem. The problem is in │ │ the %AutoIncCode GROUP. Specifically SaveAutoNumber │ │ ROUTINE. │ │ R&D: Fixed in 3009 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4185 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm:Marjolein Katsma 100276,2414 │ │ List of Suggestions and findings.... │ │ File: 4185.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4186 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When a user has "Must be in file" as a validity check for a │ │ field and he happens to delete the related file, this check │ │ is not iliminated. When code is generated a checkopen is │ │ generated with no parameters. │ │ When we delete a file, is there anyway to clean up the │ │ relations through the "must be in file" │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4187 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 61657 S8/3.0 Support │ │ 22-Mar-94 01:28:48 │ │ Sb: _Minor CSHELL BUG │ │ Fm: Rob Mousley 100075,772 │ │ To: Debby Herman 72662,475 │ │ Hi Debby │ │ Minor Bug │ │ In CSHELL, one of the utilities is Search for Text. One of │ │ the specifications │ │ that you enter is the directory for the files you want to │ │ search. This has no │ │ effect - if you want to search files in a directory, you │ │ must be in that │ │ directory, otherwise no go. │ │ Rob from Chariot │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4188 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ use a btrieve file with a key field as a byte - when you │ │ add record 91 this record does not get put in the correct │ │ key order. it gets put after record 64 │ │ ts proj 2909 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4189 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick D. Williams 72262,2720 MSG#:61815 │ │ 1)When Importing from another Dictionary the user can only │ │ import one file at a time. Why are you not able to mark │ │ several files to be copied, the same as you can when │ │ importing files from a 2.1 APP file? │ │ 2) When working in the Dictionary Editor on the Main Menu, │ │ it would be nice to have a locator field for each topic. If │ │ the user has a lot of files in the dictionary, it can be │ │ anunwanted hassle to move up and down the list to try │ │ and find the file/field/key wanted. │ │ 3)A locator field on the import from another Dictionary or │ │ aClarion 2.1 APP file. This would also save valuable time │ │ andsave on headaches looking for the file(s) that the user │ │ wants to import. Especially if the list is extremely │ │ long. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4190 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick D. Williams 72262,2720 MSG#:61815 │ │ When on a network the Build Tree option causes problems │ │ whenyou use the CShell. It locks the user in building the │ │ tree and takes forever, if you are not totally locked up │ │ first. Why not disable the tree function if the user is on │ │ a network drive or only build the tree for the current │ │ branch,not for the total network. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4191 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Try to load a text file that does not have an extension │ │ fromthe main environment screen. Example: 'TestFile.' or │ │ '*.', the file list will default back to *.cla. This does │ │ not happen loading the Editor.Exe from the DOS command │ │ line. │ │ R&D: This is a very subtle situation. What happens is │ │ that the file edit mask (e.g. '*.CLA') is not changed until │ │ a wildcard (* or ?) is detected to have been typed by the │ │ user. Changing this behavior could fix the above problem, │ │ but seems to cause even greater problems with losing the │ │ desired edit mask in other situations. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4192 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Graphics Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports problem with xyaxes() not generating xy tick │ │ marks in certain circumstances. see included examples. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4193 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : CPD21 Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If CTRL-ENTER is hit, in 2.1 STANDARD.MDL, you would go │ │ intononstop mode with the following... │ │ UPDATE; SELECT(?); SELECT; CYCLE │ │ The Form21 template goes into nonstop mode like this.. │ │ SELECT(1); SELECT; CYCLE │ │ SELECT(1) is OK, but the UPDATE needs to be there is │ │ you hit CTRL-ENTER on a field that you have just │ │ changed!!! │ │ R&D: Fixed in 3009 Template set │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4194 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The STATUS function returns 0 for a port that is CAPTUREd. │ │ Example file : 4194.zip This example assumes that you │ │ have catured a port using Novell's CAPTURE command. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4195 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This is either a bug in the btrieve driver │ │ bug in the clarion driver │ │ bug in our code in the templates │ │ An ADD to a Clarion File that posts duplicate key will │ │ clear the pointer to the file. In Btrieve it will not │ │ clear the pointer. The following code in our form template │ │ will not work correctly with a Btrieve file, if you add two │ │ consecitive records where the 2nd is a duplicate of the │ │ first. The form will not post a message because the │ │ duplicate function return false because it allows a │ │ duplicate of itself. │ │ FORM CODE │ │ IF ERRORCODE() !Error check on File I/O │ │ IF ERRORCODE() = DupKeyErr ! Duplicate key detected │ │ IF DUPLICATE(btr:field1key) !check unique keys │ │ GLO:Message3 = '[ ' GLO:Message3 = Clip(GLO:Message3) & │ │ (' btr:field1 ') GLO:Message3 = Clip(GLO:Message3)&' ]' │ │ GLO:Message1 = 'This record creates a duplicate key │ │ entry' GLO:Message2 = 'The unique key field(s) are listed │ │ below: ' │ │ ShowWarning !inform the user │ │ END │ │ see my test file 4195.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4196 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Paradox Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ using the enclosed file structure, try and add a record to │ │ this file. In database manager you will get thrown out of │ │ the program when you hit OK. In a browse, you are able to │ │ add a record but when you get back to the browse the record │ │ is not there and the edit and delete buttons are still │ │ dimmed. it is acting like it does not see the record that │ │ was just added. │ │ ts proj 2986 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4197 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Btrieve 14 preimage open error - am I using share? Yes I │ │ am. I am also using a │ │ relative file spec in my DCT. All files are │ │ '.\subdir\nnnnnnnn.dat', This │ │ caused no problem prior to 3007.2. Now my programs will │ │ notrun on a network >where there is a redirected drive │ │ referencing the "." such as 'Y:' It works │ │ just fine if the drive letter is an actual drive such as │ │ C: or D:. As it turns out VID didnot even like an actual │ │ drive. Changing the "." to a 'C:' or 'd:' │ │ or even a 'Y:' worked, but no ".'s" │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4198 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mickey Chapman 76506,551 MSG#:61893 │ │ While using the Shell tool to copy files, if you try to │ │ copyto a diskette drive that isn't ready a window pops up │ │ with the 'Ignore, Abort, Fail, etc.' message but when any │ │ of the selections are picked the shell program returns you │ │ to DOS and the DOS message: Abort, Ignore, or Fail. │ │ From Greg_W: I duplicated this problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4199 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralf Stoepper [RSR] 100021,2304 MSG#:61916 │ │ I have a problem opening Btrieve files on a Netware │ │ Runtime Server since I updated to 3007.2. It has worked │ │ with 3007.105. │ │ I am using a variable for the file name which is set to │ │ the following format: │ │ '\\SERVER\VOLUME:\DIR\DIR\FILE.EXT' │ │ Since 3007.2 CDD can't access those files and tries to │ │ create them and pops up an error message because I haven't │ │ flagged them as CREATE. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4200 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Marco Ariano 73404,1075 MSG#:62099 │ │ Why does CDD get rid of comments and indentation in .pr │ │ files? Does anyone other than me, particularly someone at │ │ Clarion, consider this 'antisocial' given that some of us │ │ handcode .pr files as is customary from a TopSpeed │ │ perspective? I understand that CDD needs to modify the .pr │ │ file, but don't understand the extent to which it does │ │ this.sincerely, Marco │ │ Marco Ariano Advanced Computing and Engineering, │ │ Alberta Research Council, Canada │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4201 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 MSG#:61575 │ │ I am having severe problems with DATE types. If I have a │ │ long or date memory variable, put it into a file field type │ │ of date and do a get(file,key)...the get will fail. I also │ │ get linker warnings about Cla$storebttime or │ │ Cla$storebtdate type inconsistency. This is causing major │ │ problems in a systwe are developing. │ │ From Greg_W: I ask for an example. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4202 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Setting up a GRAPHIC IMAGE on a Form and 'VAR1'&VAR2 is │ │ typed in DISPLAY FROM FIELD, after saving the Form, you │ │ can't get back into the Screen to make any changes to it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4203 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Select Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ calling a report with a redirect and view proc from a │ │ select template doesn't work, it doesn't get to the │ │ redirect proc, it just exits back to whatever call the │ │ select template. │ │ Take a look at the ORDERS.APP in 3007.2 │ │ R&D: Fixed with 3009 browse keycode handling │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4204 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user - ts proj3263 │ │ center('12345',4) returns a null - suggestion for the │ │ function to clip rather than to return a null. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4205 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user - ts proj 3263 │ │ msg(string1 & string2) returns a null │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4206 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ ts proj 3263 │ │ cannot pass a memo field by reference │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4207 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ ts proj 3263 - reported by user │ │ if you activate a search and replace with confirm on and │ │ accept the first couple of confirmations then cancel. Now │ │ change the confirm option to off and activate the search │ │ and replace again. The replace will not work until another │ │ file is opened. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4208 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion for a CENTER attribute for a screen variable │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4209 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user - run time halt for access to unopened │ │ files │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4210 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Paradox Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ problems with paradox driver. can not view within database │ │ manager, browse does not see any records. │ │ R&D: I can view files on my machine. How about an example │ │ file with dct that shows this. │ │ see 4210.zip, ts proj 3020 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4211 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TK DateReported : 3/24/94 │ │ Reported In : 3007 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If I blank the Screen then TYPE to it and then OPEN a │ │ Window, the TYPEd info is GONE! │ │ See test program. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4212 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Paradox Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The UPPER function is not support in the expressions for │ │ Paradox keys. Couuld be add it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4213 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/24/94 │ │ Reported In : 30073 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If the text of a radio button is touching the right side of │ │ the screen, that radio button structure will not be │ │ selected. This is true on a CUA or NON-CUA screen. See │ │ test file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4214 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/24/94 │ │ Reported In : 3004 RevisedDate : 3/24/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you have a primary key as the second field in the list │ │ box of the browse you get am Error in Floating │ │ Point, then a processor exception. -- Btrieve file. │ │ primarykey is PDECIMAL. │ │ R&D: The driver has changed _A LOT_ since 3004. Can you │ │ give me a demo program showing this still happens with │ │ 3007.2 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4215 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you have a TIME field in a screen w/ a REQ attribute, │ │ and the user enters in │ │ 24:00 (midnight) the form does not accept the number - just │ │ beeps. If you │ │ use a LONG field as a time in a screen w/ a REQ attribute │ │ and the user enters │ │ midnight, the value is correctly accepted as a valid time, │ │ but the time is │ │ incorrectly displayed as 00:00 instead of 24:00. │ │ see file 4215.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4216 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Short Description of the Problem: │ │ BackTab is not equivalent to EscKey across option fields. │ │ May cause erroneous │ │ for user │ │ see file 4216.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4217 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ TimeVar TIME │ │ TimeVar = DEFORMAT('13:50:00',@t4) │ │ TimeVar will equal zero. Must first │ │ LongVar LONG │ │ LongVar = DEFORMAT('13:50:00',@t4) │ │ TimeVar = LongVar │ │ see file 4217.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4218 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ ACCEPT ! Restores FIELD() to what was previously │ │ selected the first │ │ ! time ACCEPT_KEY is hit, but not on subsequent │ │ tries. So │ │ ! if user does ACCEPT KEY and field processing │ │ causes a │ │ ! Select(?this_field), IF the user does CtrlEnter │ │ the SELECT │ │ ! will clear field() and the ACCEPT will not │ │ restore it this │ │ ! time. │ │ see file 4218 - ts proj 3268 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4219 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/24/94 │ │ Reported In : 7.2 RevisedDate : 3/24/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If I have a C++ program with a static instance of a class │ │ linked into a Clarion application I get a warning about │ │ __INITLOOP type inconsistency. │ │ ZIP file contains a simple example of this. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4223 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 3/25/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : CPD21 Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The repeat structure of TABLE21 is having all kinds of │ │ navigation control problems. The Down Arrow will scroll to │ │ the bottom, but the bottom record will cause point field to │ │ jump to the top of the repeat structure instead of staying │ │ at the bottom. Page Down totally bombs when it reaches the │ │ bottom of the file. Test program on O:\COMMON\EDUCATE named │ │ bad21.zip. See the README.cla file in the zip file. │ │ Thanks... │ │ R&D: Fixed in 3009 version of REPEAT.CLA │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4224 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 3/25/94 │ │ Reported In : 3007 RevisedDate : 3/29/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests ability to disable skip on @t3 and @t6 │ │ R&D: These picture tokens are not explicitly supported for │ │ entry of data. Although it appears that they will work for │ │ entry, not every case actually works correctly, such as │ │ entering 12:30 and trying to get it to be PM instead of AM. │ │ In addition, to support these tokens would imply support │ │ for similar date tokens, which would in turn be far more │ │ complicated to implement. │ │ The inadvertant ability to get fields with picture tokens │ │ of @T3 and @T6 into generator screener by using populate │ │ will be fixed. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4225 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/25/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : PenDOS Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be nice to be able to trap for some error to │ │ determine whether or not PenDOS is loaded before running a │ │ Pen program.. Running a Pen program w/o PenDOS loaded can │ │ cause a major lockup to occur... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4226 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/25/94 │ │ Reported In : 30072 RevisedDate : 3/25/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : REPORT ENGINE │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Larry Teames 73150,104 MSG#:62281 │ │ START_DATE LONG (contains 3/22/94) │ │ A report (PRE(RPT)) field defined as: │ │ DATE Col(55) STRING(@D4) │ │ A report code statement of: RPT:DATE = CUS:START_DATE │ │ Yields: July 04, 1901 <---!!!! │ │ In other words, looks like the D4 picture, when defined _in │ │ the report structure_ doesn't work correctly. │ │ From Greg_W: I duplicated this problem and created a test │ │ file (4226.zip). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4228 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rod Smith 74230,3451 │ │ Disable function will work to disable a field within a │ │ repeat structure, however the disable color does not │ │ display. See example file │ │ 4228.zip │ │ tech-debby │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4229 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Larry Teames 73150,104 MSG#:62513 │ │ Based on prior experimentation, I discovered that PROTMODE │ │ writes what would be the equivilent of what's written to a │ │ CPD 2.1 CLAVMx specification (ie. screen saves, memory │ │ queues, etc) to the CLATMP environment variable as well. │ │ Usually not a problem if you have significant EMS/XMS, but │ │ can be a problem if little is available and CLATMP points │ │ to a RAMDRIVE and the RAMDRIVE fills up. Then it yields an │ │ XTRACE. │ │ Larry Teames -- Creative PC Solutions -- AZ CUG │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4230 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tom Hebenstreit 72154,731 MSG#:62634 │ │ Please file as a suggestion that some method be implemented │ │ for alerting us as to which fields need us to enter the │ │ quotes and which don't. It's a pain to either have to │ │ remember each prompt's requirements or constantly get these │ │ kind of compile errors. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4231 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : DBase III Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:62523 │ │ I know you guys are about to replace the db3 driver (not │ │ before time) - here's more motivation... │ │ Consider a file with an index. │ │ The index needs to be built. The index field in some of │ │ the file's records is zero or blank. The BUILD will always │ │ bomb out with │ │ 'Out of range error' │ │ code 4 │ │ clarion error code 404. │ │ Roll on the new driver! │ │ Rob from Chariot │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4232 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Project System │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 62597 S17/Priority Support │ │ 25-Mar-94 14:27:27 │ │ Sb: #pragma define │ │ Fm: Joe Impac 71477,3013 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ We've run into a problem w/ compiler switch defines. Once │ │ you get past eight │ │ #pragma define(thisflag=>on) type statements the Clarion │ │ project file destroyer will remove all but the first four │ │ defines. You can get around this by putting │ │ your defines in an include file, and the defines will be │ │ read by the compiler, but the value of of later defines │ │ appears to always get read as off (0) even if the pragma │ │ sets it to on. If you start to add even more, the define │ │ is completely ignored. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4235 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 62440 S17/Priority Support │ │ 24-Mar-94 20:12:39 │ │ Sb: Btrieve & LOGOUT │ │ Fm: Joe Impac 71477,3013 │ │ To: Debby Herman 72662,475 │ │ LOGOUT does not post any error messages in the Btrieve │ │ driver, and does not │ │ seem to be working correctly. Following scenarios are with │ │ Brequest and │ │ Btrieve.NLM 6.1 │ │ Scenario 1. │ │ User A does a LOGOUT(.1,file) < no error posted > │ │ User A does an ADD < no error posted > │ │ User B does a LOGOUT(.1,file),< no error posted > │ │ User B does an ADD < User B is now hung until User A │ │ COMMITs or ROLLsBACK> │ │ < After User B does COMMIT or RollBack │ │ - no error │ │ posted> │ │ Scenario 2. │ │ User A does a LOGOUT(.1,file) < no error posted > │ │ User B does a LOGOUT(.1,file) < no error posted > │ │ User B does an ADD < no error posted> │ │ User A does an ADD get's stuck like User B did in Scenario │ │ 1 │ │ Basically, there is no way to tell if another user has │ │ locked a file. │ │ -cindy cohen IMPAC Medical Systems │ │ Scott: This seemed to work okay with the TSR but not the │ │ NLM. See file 4235.zip. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4236 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/28/94 │ │ Reported In : 3008 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ ERASEing fields does not clear fields w/ the @P or @K │ │ pictures. │ │ Also, in the same test program, using CLEAR(field) DISPLAY │ │ does some funny things on the screen too. For example if │ │ the field is full the last character in the field remains │ │ on the screen. │ │ This is for all String types! │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4237 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RI code (record clearing) not correctly handling reverse │ │ order keys. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4238 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Question │ │ │ │ Section : Report - Runtime │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: GREG VERNON 71223,1011 MSG#:62627 │ │ I have a program running on a computer that is linked to │ │ an HP3000. The link is for disk storage purposes and access │ │ to a laserjet. The lan software sets up the printer ports. │ │ There is no direct connection to the printer. The problem │ │ is when I print a report, a hardware problem management │ │ window comes up and says device not responding. If I press │ │ the fail button, the report will print, but the window │ │ doesn't close. There is no problem with any other software │ │ printing to the laser. │ │ I called Clarion tech support on Fri. The guy │ │ I spoke to said that Clarion is trying to communicate with │ │ the printer. His suggestion was to change my printdevice │ │ to PRN, which may print out LPT1. I recieved the same │ │ error. He also said, try printing to an ascii │ │ file, then copy the file out the port. I have not been able │ │ to figure out how to copy this file. Can you help? │ │ Thank you │ │ Greg │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4239 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/29/94 │ │ Reported In : 3007 RevisedDate : 3/29/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : General Environment │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The mouse sensitivity in the Environment is not very good. │ │ I would like a way to increase the sensitivity so I don't │ │ have to move the mouse a mile to get it to move half way │ │ across the screen. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4240 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/29/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Build() for key or file failing on a key with OPT attrib │ │ and all records have been opted out of the KEY. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4241 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : QA DateReported : 3/29/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Unlock() hanging system if file was not previously Lock()ed │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4242 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : JB DateReported : 3/29/94 │ │ Reported In : 30072 RevisedDate : 4/01/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : View Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports when a Report is printed from the View │ │ template, formfeeds occur between pages │ │ R&D: Does the user have a FormFeed on each page of the │ │ printed report, or is page overflow the way forms are │ │ fed? │ │ Does the VIEW have a Form Feed in it? │ │ If the number of lines for the VIEW report the same, │ │ or less than the number of lines for the report? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4243 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/29/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Screen Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 28-Mar-94 09:33:36 │ │ Sb: radio buttons │ │ Fm: Jon B. Bushey 71521,2267 │ │ To: sysop (X) │ │ When placing radio buttons on a form, there is a problem │ │ when there isn't enough room. If there is not enough room │ │ remaining to the right, (field bleeds right off window) │ │ youget stuck in an endless loop of fld to OK to fld to OK to │ │ fld to OK - cancel button does not work. │ │ Tech support note: You are not completly stuck as you can │ │ press the attribute button and change the row and column. │ │ However when you do this it still tries to place it │ │ outside the window. It moves it over when you hit the ok │ │ button. Seems it should let you escape. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4244 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/29/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Suggestion │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Sb: #dictionary not req. │ │ Fm: Jon B. Bushey 71521,2267 │ │ To: sysop (X) │ │ In Generator, the dictionary should not be required. There │ │ are many times when │ │ our programs do not require a dictionary. One example is a │ │ program we wrote to │ │ use the findfirst and findnext directory functions. It │ │ does not use any files. │ │ It simply builds a queue of matching file names. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4245 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In local data for a procedure I would like to Copy a Queue. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4246 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In local data, you are not allowed to have a field by the │ │ same name even when the field is part of a queue with a │ │ different prefix. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4247 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Set default colors and Reapply default colors have │ │ different prompts for the same exact functionality. I am │ │ referencing the screen formatter and the pulldown │ │ formatter. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4248 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Question │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A pulldown menu acts different base on whether or not the │ │ screen that is opened at the time is graphic or not. │ │ For example: │ │ If I currently have a text screen open, then I open a │ │ graphic screen, on top of that I open a pulldown. Now I │ │ close the graphic screen. Instantly the pulldown is │ │ displayed. │ │ If the graphic screen is opened before the pulldown and │ │ then closed, the pulldown does not redisplay until it │ │ reaches the accept statement. │ │ The question is: Was this intended to work this way? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4249 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 7002 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The option for overprint next is in a different place for │ │ the editor vs the Generator. Could we make it consistant? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4250 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the entries for USE & LABEL are in reverse order for TEXT │ │ fields when compared to CONTROL and DATA fields. │ │ Could we be more consistant? │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4251 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Tracking is the subject: │ │ When looking at the sample that is given for MIXED 1, the │ │ right hand side of the intersection appears normal but when │ │ placing it on a report I get a smooth mouse character. │ │ R&D: This appears to be a case where a right hand │ │ intersection was actually a center character. Because the │ │ character was remapped, it was thought to be a right hand │ │ intersection. Solution is simply to space out the │ │ character and redraw it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4252 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the report formatter, Drawing a SINGLE track │ │ horizontally from right to left, while you are directly │ │ below a BAND, when you arrown down you get a partial line │ │ up twords the band. │ │ To reproduce, do this in the botton band in the report, │ │ with only a single line open, and press down arrow twice. │ │ This first down arrow makes the proper turn downwards. The │ │ second down arrow scrolls the entire report down one line │ │ and causes the tracking to turn upwards. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4253 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you place control sequences right next to each other │ │ then try to copy them to other locations, lets say two │ │ lines down. Strange things have happened. Both will │ │ change to the same thing or they will not save after you │ │ exit. (there is a posibility that this was in the editor) │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4254 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Generator │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 62908 S8/3.0 Support │ │ 28-Mar-94 10:14:29 │ │ Sb: Compile Crash /Suggestns │ │ Fm: Mark Goldberg 75250,2551 │ │ To: Debby Herman 72662,475 │ │ There should be a simple way to show the value of a radio │ │ button'd field using appgen's screener. Currently I have to │ │ exit screener, go nto the data otheron, create a field │ │ LIKEit (simulating the like as appgen doesn't support │ │ the like attribute) and then place the field OVER the │ │ original field, exit the data section, return to │ │ screener and then place the field on the screen as an │ │ entry field, mark it as a skipped field, and then change │ │ the color from my entry color to my display color, and then │ │ press esc when the prompt comes up, then ^K to my display │ │ prompt color and key in the display prompt directly on the │ │ screen (I don't use prompts on display fields, because I │ │ don't want the hot-letter to show and effect flow, when │ │ I can never actually select the field). │ │ a) allow modification of the data │ │ section from within the field selection │ │ screen (after I've pressed │ │ insert/entry field) b) add like support to the │ │ data section (and data dictionary) │ │ [I understand there are │ │ issues surrounding the order of field │ │ declaration] │ │ c) support a default color │ │ for display fields [consider a screen │ │ structure type: display vs. entry/skip] │ │ d) remove hot-letters │ │ from skip'd prompts (sorry if done in 3007.x) │ │ [in general allow a │ │ prompt to have NO hot-letter] │ │ Additional suggestions: │ │ a) add exit without │ │ save from the data section b) add Relational │ │ Integrity to field re-naming between the data-section │ │ and screener │ │ c) allow the field │ │ names to be editted within screener ex: unit_type │ │ -> lcl:unit_type or unit_type[1] -> unit_type[2] │ │ d) allow the │ │ field type to be modified for a field within screener │ │ (probably │ │ only useful if display becomes a seperate field type) │ │ (well, how │ │ about entry <-> radio button ?) e) move │ │ prompt editting inside of the field screen (at │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4255 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 62908 S8/3.0 Support │ │ 28-Mar-94 10:14:29 │ │ Sb: Compile Crash /Suggestns │ │ Fm: Mark Goldberg 75250,2551 │ │ To: Debby Herman 72662,475 │ │ Hi Debby, │ │ When I compile I get an error message followed by a crash. │ │ 'Error: Embedded OVER must name field in same structure' │ │ 'WARNING! Error In Floating Point Value. Press Any Key To │ │ Continue' │ │ 3006 -> followed with a runtime.$$$ │ │ 3007.1 -> Gives me a Protection Violation Screen │ │ Amazingly after the Protection Violation I'm still running │ │ (the compile │ │ ended, but I can edit errors etc. │ │ The code that causes the situation: │ │ Unit_Group Group,DIM(3) │ │ Unit_Type string(11),OVER(cls:Unit_Type) │ │ . │ │ Admittedly this is illegal code. I was trying to display │ │ the value of a radio │ │ button (as a string) three times on a screen, which is why │ │ I was why I wrote │ │ this dain bramaged <G> code in the first place. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4256 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ problem with either set(key,key) or previous. see 4256.zip │ │ cla file explains further │ │ ts proj 3293 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4257 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/31/94 │ │ Fixed In : Status : Need/Info │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If I delete the keys for an application, then try to add a │ │ record in a form, a checkopen rebuilds key files, and then │ │ my autonumber field contains ZERO instead of the next │ │ consecutive sequence number. If I exit the form, and try │ │ to add again everything is OK. This can be seen in the │ │ CHECKBOOK application. │ │ R&D: I need to know the following information: │ │ 1. How is the user getting to the form without going │ │ through a browse. If the user is going through a │ │ browse, why isn't %Primary opened in the Browse? │ │ Ask the user to check the File layout in the │ │ browse. │ │ 2. What file driver is the user using for %Primary? │ │ If the user would provide code, it would be very │ │ helpful. I cannot get this to reproduce in CheckBook │ │ application (with 3007.2 templates and install set). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4258 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/31/94 │ │ Fixed In : Status : NotaBug │ │ │ │ Section : Clipper Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In driver.doc...there is no mention of 'LONG', yet long is │ │ available in the data dic. Is it really available? │ │ Tech support note: I can create a file with a long. If │ │ this is valid, driver.doc should be updated. │ │ debby │ │ R&D: Long is not really available as a general data type. │ │ In dBase when defining a memo you need to define a pointer │ │ in the record structure to point to the memo. This field │ │ can be either a LONG or STRING(10). IT MUST NEVER BE │ │ EDITED or really used. So yes you can have longs, but you │ │ can't use them. So the documentation is correct. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4259 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Clarion Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 62941 S8/3.0 Support │ │ 28-Mar-94 14:16:33 │ │ Sb: empty build -> xtrace │ │ Fm: Martin Wehlou (Cactus) 72047,2444 │ │ To: Debby 76711,1034 │ │ Debby, │ │ Batch 3007.2, Clarion file driver, dos extender protected │ │ mode, no runtime │ │ libraries, making exe. │ │ Doing a build(filelabel) on a file with no records causes │ │ an xtrace. │ │ -- Martin [Cactus Computing bvba - Belgium] │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4260 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 28-Mar-94 20:52:24 │ │ Sb: Btrieve file sizes │ │ Fm: Joe Impac 71477,3013 │ │ To: Debby Herman 72662,475 │ │ Debby or Scott, │ │ While testing some file conversion programs I ran into an │ │ interesting │ │ occurence. I am converting a Btrieve file (record length │ │ 145, 3 keys all dups, pagesize 3584, 27 records) to another │ │ Btrieve file ( record length, 168, 3 keys │ │ all dups, pagesize 4096) I am using Btrieve.NLM 6.1(c i │ │ believe) and Brequest 6.1d. If I run only this conversion │ │ program the new file is created and is 86016 bytes. If I │ │ run other conversion programs before and after this one │ │ (using a for loop), the resulting file has turned out to be │ │ 65536 bytes, 77824 bytes, 94208 bytes. The contents of the │ │ files appears to be accurate. I'm not losing any data. │ │ Could someone explain what causes such a fluctuation in │ │ file sizes? │ │ Thanks │ │ -cindy cohen IMPAC Medical Systems │ │ Tech note: Scott, I logged this for reference. I have │ │ asked Cindy to see if she gets the same results with the │ │ TSR. I will add the information when I get it. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4261 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/30/94 │ │ Reported In : 3008 RevisedDate : 3/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : FoxPro Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ extended mode application using fox files, locks up after │ │ viewing a few records. in overlay mode, no lockups occur. │ │ read readme file in 4261.zip │ │ R&D: I cannot reproduce the problem using the current │ │ source. The heap cheacker reports no detectable memory │ │ corruptions. So all I can assume is that this has been │ │ fixed by one of the other fixes │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4262 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/30/94 │ │ Reported In : 3004 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report - Runtime │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Reported by user:When issuing a control code for hewlett │ │ packard overlays to a file than append a report to that │ │ file then print that file as a textfile to the printer. On │ │ page two and every page after, the second line is skipped, │ │ ie. line 3 is brought to line 2. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4263 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Miscellaneous │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ this app Consists of multiple dlls. when run as each dll │ │ is loaded the program runs slower and slower. see me for │ │ documentation the user sent in. user says that this │ │ problem did not exist in 3005, but when 3006 came along │ │ there was a noticible difference in speed as the dlls get │ │ loaded │ │ ts proj 3228 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4264 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 3/31/94 │ │ Reported In : 30072 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If an Extended applicatin does a BUILD() on an empty │ │ Clariondata file, it will always Xtraces, if it's done with │ │ Overlays, it works fine. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4265 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : GW DateReported : 3/31/94 │ │ Reported In : 30072 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There are 2 known bugs with the BUILD on Clarion Data files │ │ that may cause GP errors or Loader failures. │ │ 1)If all key components for a KEY are set to their highest │ │ value. ie, If a numeric key component has a -1 value or a │ │ string key component has a FFh value for each character. │ │ Meaning any key that has a value in which all bits are set │ │ ON. │ │ 2)If you BUILD(FILE) and this file has at least 2 keys. If │ │ a key ends up being empty (no key records) as a result of │ │ the build process it will crash on the next key it tries to │ │ b╩╦ld. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4266 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/31/94 │ │ Reported In : 3008 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RPTTST.CLA contains an example of a report structure. if │ │ you format the report and save it you will see that a │ │ control field dissappears from the structure. │ │ tsproj 3314 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4267 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 3/31/94 │ │ Reported In : 30072 RevisedDate : 3/31/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Key on a PSTRING. Display that file in a browse using that │ │ key. Arrow to the last line of the browse. That last line │ │ will be duplicated... See test file. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4268 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DH DateReported : 3/31/94 │ │ Reported In : 3008 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Btrieve Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 62997 S8/3.0 Support │ │ 28-Mar-94 17:41:21 │ │ Sb: XTRACE On Database │ │ Fm: Barry McClure 75170,1100 │ │ To: Greg Whitaker 76711,1035 (X) │ │ Greg, │ │ A couple of weeks ago I reported a bug that generated │ │ an XTRACE │ │ when opening a file using Database under OS/2.1 for │ │ Windows. You may │ │ be able to replicate it. │ │ 1) Make and run an application that is using Btrieve │ │ drivers. │ │ 2) When the program is running, open a file (Browse) │ │ for │ │ example. │ │ 3) Quit the program, return to the IDE, and select │ │ Database │ │ 4) Open the same file from the Database │ │ 5) Chances are you'll never see your data on the │ │ screen. The │ │ wings will fall off CDD and you'll probably crash │ │ with an │ │ OS/2 error. (Make sure you're wearing a seatbelt │ │ or have │ │ someone tie you to your chair.<g>) │ │ Now if you don't run the application, but go straight to │ │ Database │ │ and open the file, no crash will occur. I suspect the │ │ problem is │ │ related to the Btrieve drivers. │ │ Barry... │ │ Tech Note: Pam was able to reproduce this bug. Attached is │ │ a btrieve app she used. │ │ Debby │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4269 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : PB DateReported : 3/31/94 │ │ Reported In : 3008 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Formatter - Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ linecounter seems to be incremented incorrectly. │ │ using 4269.zip the report structure consists of 8 lines. │ │ before printing the detail section linecounter = 1. after │ │ the detail is printed linecounter = 0 and if the detail is │ │ printed again linecounter = 8 when it really should be 15. │ │ in 2.1 the linecounter gives values of 1,8,15. in 3.0 │ │ linecounter gives values of 1,0,8 │ │ ts proj3314 │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4270 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : NA DateReported : 3/31/94 │ │ Reported In : 30072 RevisedDate : 3/31/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Browse Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Duplicated user problem: (see 4270.zip for example) │ │ Using a paradox driver, in a browse template, and enabling │ │ hot records, the following occurs: │ │ 1 If you change a record, the highlight bar moves to the │ │ last record in the list box upon return from the form. │ │ 2 If you mouse click on the OK button to complete the │ │ form, the record is changed but not sorted and the form │ │ pulls up the next record as if to change it. If the Ok │ │ button is pressed on the form 'Record Not Available' is │ │ produced. │ │ 3 The sort is always case sensative │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4272 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/01/94 │ │ Reported In : 30072 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 MSG#:63238 │ │ Using CDD 3007.2, an ENTRY field with a picture of │ │ @N-9.2 acts much different than CPD 2.1 and as described │ │ on page 3-19 of the LRM. Clarion has always had the │ │ strange way of throwing the minus sign clear to the left │ │ edge of the field during entry, but always │ │ brought it back to immediately left of the number once │ │ the field was completed. However, now it stays clear to the │ │ left of the entry field boundary after completion. This │ │ is very confusing to the user and certainly not the way │ │ I would expect (or want) it to work. Am I missing │ │ something, or can this be added to the 3008 to-do list? │ │ Thanks, │ │ Joe Bouterse Creative │ │ Solutions, Inc. Indianapolis, IN │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4273 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : DB DateReported : 4/01/94 │ │ Reported In : 3008 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This program will make the compiler take a very strange │ │ DMP... │ │ PROGRAM │ │ MyMemo MEMO(3850) │ │ MyRow GROUP,STRING(70),DIM(55),OVER(MyMemo) │ │ . │ │ CODE │ │ RETURN │ │ See Test File.. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4274 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TM DateReported : 4/01/94 │ │ Reported In : 30072 RevisedDate : 4/01/94 │ │ Fixed In : Status : Fixed │ │ │ │ Section : Pulldown Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Pulldowns not issuing calls to open files specified in the │ │ file schematic. │ │ R&D: Repaired in 3009 templates │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4275 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 4/01/94 │ │ Reported In : 3008 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report - Runtime │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When trying to print a large Memo field and the contents of │ │ the Memo field span more than one page, the Page Header │ │ doesn't get printed on the second page but the Page Footers │ │ are being printed at the bottom of the pages. │ │ 4275.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4276 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 4/01/94 │ │ Reported In : 3008 RevisedDate : 4/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Editor │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ On any blank line in the Editor while in BLocK mode..... │ │ Press Ctrl-D, then press Home. │ │ You will be taken to column 256 with garbage displayed. If │ │ you click the mouse on any part of the screen, you will │ │ Xtrace. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4277 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BF DateReported : 4/01/94 │ │ Reported In : 3008 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Documentation │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ With the file size of DRIVER.DOC growing ever larger, do │ │ you think it might be a good idea to begin seperating file │ │ driver docs into seperate files (Like the templates). You │ │ could then have CLA21.DOC, BTRV.DOC, FOX.DOC, etc. The │ │ programmer could also selectively install or delete │ │ documentation that he does not need... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4278 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/01/94 │ │ Reported In : 30072 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Dictionary │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Will Fastie 76655,1566 MSG#:63346 │ │ I'd like to be able to import the entire contents of a │ │ dictionary in one fell swoop, not a file at a time. In │ │ otherwords, a merge of two dictionaries into one. Perhaps │ │ this capability already exists and I just haven't found │ │ it. I've been doing it one at a time. Will │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4279 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 4/01/94 │ │ Reported In : 3008 RevisedDate : 4/01/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If FOREGROUND ONLY is checked on in the field properties │ │ fora PROMPT, an invalid screen structure results during │ │ runtime │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4280 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : J DateReported : 4/01/94 │ │ Reported In : 3007 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : DOS Driver │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggests an error be generated when unsupported │ │ functions are used, i.e. HOLD │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4281 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/01/94 │ │ Reported In : 30072 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: E.J. Tejera 71066,1361 MSG#:63480 │ │ Suggestion: Allow for deleting entire lines in memos │ │ without having to have wordwrap enabled. │ │ Message: │ │ Ah! we must be using the few that don't fit in "almost │ │ always" <g>. A good example is capturing technical (very │ │ formatted) output from outside sources. If wordwrap is on │ │ it will almost always <g> trash the column formatting. │ │ I very much need to be able to delete a line even if not │ │ using word warp │ │ Eric. PS. As the sage said : "Wordwrap or not delete a line │ │ from time to time you must" │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4282 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TB DateReported : 4/02/94 │ │ Reported In : 3008 RevisedDate : 4/02/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When on a field that has the immediate attribute and you │ │ are in insert mode, after going through this field and back │ │ tabbing to it, pressing a hot key or choosing a button with │ │ the mouse no longer functions. For an example see 4282.zip │ │ and read the readme.txt for exact instructions with the │ │ program that has been presented. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4283 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Suggestion │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Marjolein Katsma 100276,2414 MSG#:63860 │ │ There is no symbol for the RECLAIM attribute on a File │ │ either; should work just like %FileCreate (and be named │ │ %FileReclaim). │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4284 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Language Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Nick Van Eldijk 71613,544 MSG#:63828 │ │ Problem with BUILD and the Clarion File Driver. │ │ Following a Clarion file-definition with a │ │ 'test'-procedure. This procedure creates a file as big as │ │ you want. I tried with 30,000 records and that went fine. │ │ With 90,000 (probably earlier) there is the 'Overlay loader │ │ fatal error 8501'. │ │ I think a │ │ 'self-creating-file-procedure' as below can be very │ │ convenient for passing test-results etc. (don't have to │ │ pass huge files). This is just something I put together to │ │ show you. Maybe some others will jump in to perfect the │ │ idea... │ │ tst_data │ │ file,pre(tst),driver('Clarion'),create,reclaim,| │ │ name('tst_data.dat'n1_ptr │ │ key(+tst:n1),nocase n2_1_ptr │ │ key(+tst:n2,+tst:s1),dup,nocase n2_2_ptr │ │ key(+tst:n2,+tst:d1,+tst:s1),dup,nocase record │ │ record n1 │ │ long !@n08 (unique number) n2 │ │ short !@n3 (group │ │ number) d1 long !@d2- │ │ (date mm-dd-yyyy) s1 string(40) │ │ !to be filled with random │ │ !characters =>65 =<90 dec1 │ │ decimal(10,2) !just for fun │ │ end end │ │ the procedure: │ │ make_data procedure │ │ random_string string(40) │ │ string_ptr byte,dim(40),over(random_string) │ │ n1 long │ │ count byte │ │ code │ │ setcolor(7) │ │ show(1,1,clock(),@t1) !time start of │ │ creating file open(tst_data,22h) │ │ if errorcode() = NoFileErr !(NoFileErr is │ │ 2) create(tst_data) │ │ open(tst_data,22h) │ │ end │ │ stream(tst_data) │ │ set(tst_data) │ │ loop n1 = 1 to 90000 !I think │ │ 60,000 is enough next(tst_data) │ │ tst:n1 = n1 !like a │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4285 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Screen Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Eric Babcock 71630,560 │ │ To: Debby Herman 72662,475 │ │ > Virtual Screen Movement is Poor in Compiled Programs. │ │ If three sides of a virtual screen extend off-screen and │ │ you move toward the │ │ side with two adjoining sides that extend off-screen, the │ │ curser will jump down │ │ and to the right, making it impossible to perform a smooth │ │ panning motion. │ │ Users attempting to use check boxes or radio buttons in a │ │ column donw th eright │ │ side of the screen will have the mouse continually shift to │ │ the outside and │ │ down. │ │ The Screen Formatter in the Editor or the IDE handles │ │ virtual screen movement │ │ perfectly. Only compiled exe's show the movement problem. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4286 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : API Library │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Leschak (CompuSyste 71461,471 MSG#:63304 │ │ i cannot seem to get the SetError API call to function │ │ properly...the following code examples is how i am using │ │ it... │ │ SAV:ErrorCode = ERRORCODE() │ │ ... │ │ SetError(SAV:ErrorCode) │ │ TYPE(ERRORCODE()) !is not the │ │ same as SAV:Errorcode. │ │ From Greg_W: │ │ I duplicated this problem: Seems like Setting errorcode to │ │ 0 is returning 318. Example file: 4286.zip │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4287 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Form Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: MONICA M. MANUELL 75110,1007 MSG#:63357 │ │ In my BTrieve file description I have a dimensioned group │ │ around two fields: TestGroup Group, Dim(10) │ │ Code String(2) │ │ Desc String(20) │ │ Unless I move the dimension inside the group and put it on │ │ each individaul field, the form template generates compiler │ │ errors "Internal Error" ISL 192 and ISL 193. The │ │ applicationgenerator allows me to place the fields on the │ │ screen though. In addition when referencing these │ │ fields in embedded code, I get the error that I have │ │ an incorrect number of dimensions on my variable... │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4288 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : BN DateReported : 4/04/94 │ │ Reported In : 3008 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Cshell │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you run CSHELL(under os/2) from the enviroment and │ │ changeto the CLARION3 directory, then search for a word, you │ │ will get a SYS3175 error. │ │ If the same thing is done from the prompt it xtraces. │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4289 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Report Template │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:63524 │ │ I've spotted a problem in the rptgrps.tpx. │ │ Consider a report procedure. Only one file is declared for │ │ the report. The key has three fields and group breaks are │ │ declared on fields 2 and 3. The fields are called Code, │ │ Destination and Origin │ │ There are no fields in the body. Origin and Destination │ │ are placed in the Destination group footer. Several total │ │ fields are placed in the Origin group footer. So: │ │ Origin group header---------------- │ │ Destination group header-------- │ │ Detail------------------------------------ │ │ Destination group footer-------- │ │ Origin field, Destination field │ │ Origin group header---------------- │ │ Total fields,..... │ │ All works well, except if the last record is the only │ │ record in a specific destination, with a specific origin. │ │ The ErrEndFileFlag# is set and the │ │ Print::Pre::GroupFooters routine is called. Normally, if it │ │ is not End of File, Save::Pre::Groupfooters routine is │ │ called. │ │ This puts the old record │ │ values into the buffer which is then printed in the │ │ Print::Pre::GroupFooters routine. This is good │ │ except... if the End of File is reached, so that the group │ │ break for the last record has the same values in the two │ │ breakfields as the last record printed in the previous │ │ destination group break. I │ │ have attempted to fix the problem in the template, and it │ │ works fine for the number of reports I am running. But I'll │ │ leave the testing up to you... <g> │ │ The change that I have done is on line 901 of the │ │ RPTGRPS.TPX. Just before the PRINT::%FilePre::GroupFooters │ │ routine is called, I inserted a line │ │ Save::%FilePre::FooterFields. │ │ I hope I have explained │ │ myself well enough for you to duplicate the problem. │ │ Katja │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4290 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Misc. Templates │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:63520 │ │ You probably know about this already but... │ │ In 3007.2's BrowseGrps.tpx you need to add the following at │ │ line 920: │ │ OF ?LIST │ │ #IF %ScreenFieldEdit │ │ %ScreenFieldEdit │ │ #ENDIF │ │ ...Just to get the When field is completed code to │ │ generate! │ │ Cheers │ │ Rob from Chariot │ │ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────┐ │ C.D.D. 3.0 ProblemNumber : 4291 │ ├───────────────────────────────────────┴───────────────────────────────┐ │ Reported By : TK DateReported : 4/04/94 │ │ Reported In : 3008 RevisedDate : 4/04/94 │ │ Fixed In : Status : Problem │ │ │ │ Section : Compiler │ │ │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Having an OMIT prior to the Program statement in a │ │ multi-module program, the compiler does not compile all the │ │ other modules. The error returned refers to the OMUIT() │ │ directive. │ │ Moving the Program statement to the first line of the main │ │ module all modules ompiler OK. │ │ │ └───────────────────────────────────────────────────────────────────────┘